Inconsistent feature name
MarcoCicognani opened this issue · 2 comments
MarcoCicognani commented
Hi, very good crate, it as undergone a strong improvement from the version 0.5 that is use.
As i said in the title i noticed that the lock_api feature is named lock_api1 into the code, making impossible for the users to enable that feature.
Keep it up!
zesterer commented
This is such that the feature does not conflict with the crate name, but I can realias the crate name. I'll put that on my list of things to do!