Sebastian Thiel

It's true - to make this work one would have to prevent ending up with the `curl` feature in the first place, so the respective cargo features would have to...

The one used by `cargo-smart-release` was available first. If I remember correctly, `tame-index` has additional fixes and might generally be better. Both are maintained, but `tame-index` gets features more actively.

> @Byron that much is clear from the readme in `tame-index`; it literally starts out with stating everything that is wrong in `rust-crates-index`. The question is, was there some sort...

I think it would be feasible to add a new method that has the fuzzy lookup behaviour, and contributions for this would be very welcome.

What about… adding a permutation iterator? Given a name, it will permute through the possible settings of `_` and `-` and produce a new name on each call to `next()`...

I think that if there was a way to instantiate a `GitIndex` without auto-initialization, maybe by returning `None` if the index doesn't exist, that would allow the caller to know...

Apologies, this issue was auto-closed which wasn't actually my intention nor my doing even though GitHub claims it was 😅. Could you recheck to see if the issue is fixed...

I think this should be fixed by now and I'd appreciated if the issue could be re-evaluated [against v2.0](https://docs.rs/crates-index/2.0.0/crates_index/). Thank you.

> So `gix` blocks instead of errors, right? No, `gix` doesn't, but this library now uses locks to protect itself from… itself. I might have geared that specifically to make...

Thank you! I went with option 2: "Document it in the API" which now makes clear that opening an index isn't safe in concurrent contexts due to the implicit auto-cloning....