You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dyn_safe crate is published on crates.io and it's README recommends to use it for indented purpose. It also has MSRV, license and additional Cargo metadata filled in, just like what is expected for a typical Rust library.
But version number is 0.0.2, which is below even the default 0.1.0. Such version number typically suggest deeply experimental state of a crate, deterring even not very serious usage. Such extremely low version numbers also prevent publishing compatible updates that, for example, just improve documentation.
So what is the status of dyn_safe project? Is it recommended to depend on it? If yes, the crate should be re-published as e.g. 0.1.0 (or even 1.0.0, if somebody tried and tested it and is using it for a while without problems). If no, than README should warn about it and mention possible problems.
The text was updated successfully, but these errors were encountered:
You're right, it started as an experimental crate, but the feature is simple enough that there are no blockers whatsoever w.r.t. stabilization; I shall make a 1.0. release in the incoming days 🙂
dyn_safe
crate is published on crates.io and it's README recommends to use it for indented purpose. It also has MSRV, license and additional Cargo metadata filled in, just like what is expected for a typical Rust library.But version number is
0.0.2
, which is below even the default0.1.0
. Such version number typically suggest deeply experimental state of a crate, deterring even not very serious usage. Such extremely low version numbers also prevent publishing compatible updates that, for example, just improve documentation.So what is the status of
dyn_safe
project? Is it recommended to depend on it? If yes, the crate should be re-published as e.g.0.1.0
(or even1.0.0
, if somebody tried and tested it and is using it for a while without problems). If no, than README should warn about it and mention possible problems.The text was updated successfully, but these errors were encountered: