seqlock Make 1.0 version?

Since the API hasn't changed much in ~5 years, could this crate be bumped to 1.0?

Crates implementing concurrency primitives with version numbers < 1.0 look (justifiably) scary, which I don't think should apply to this crate.

Mar 16 '21 02:03 Valloric

I'm not really actively developing this crate, so I don't feel comfortable releasing it as 1.0. In any case the version is only an indicator of breaking changes in the API, it doesn't necessarily reflect the quality of the crate. There are many widely used concurrency-related crates such as parking_lot which have a version number < 1.0.

Mar 17 '21 23:03 Amanieu

In any case the version is only an indicator of breaking changes in the API, it doesn't necessarily reflect the quality of the crate.

To you and me, yes. But not to everyone. And sometimes those others are decision makers.

There are many widely used concurrency-related crates such as parking_lot which have a version number < 1.0.

Frankly, this isn't an argument for keeping this crate < 1.0, it's an argument for bumping parking_lot to 1.0. :)

Mar 18 '21 00:03 Valloric