These are chat archives for rust-lang/rust
log = "0.3.6"as the only dependency, and build, Cargo downloads and compiles in both log v0.4.1 and v0.3.9. Am I the only person who thinks that may be crazy?
[[package]] name = "log" version = "0.3.9" source = "registry+https://github.com/rust-lang/crates.io-index" dependencies = [ "log 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)", ]
rand = "0.4.1"(where 0.4.2 is the latest) and Cargo definitely just picked up 0.4.2.
log = "<=0.3.8"
error[E0277]: the trait bound `T: std::marker::Sized` is not satisfied --> src/main.rs:4:46 | 4 | struct Opaque<T: Sized>(PhantomData<T>, [u8; mem::size_of::<T>()]); | ^^^^^^^^^^^^^^^^^ `T` does not have a constant size known at compile-time | = help: the trait `std::marker::Sized` is not implemented for `T` = help: consider adding a `where T: std::marker::Sized` bound = note: required by `std::mem::size_of`
log = "0.3.8"will just make it use the most recent compatible release
=0.3.6. I think bspeice wanted 0.3.6 specifically.
0.1.2shouldn't be compatible with
Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.
Patch version Z (x.y.Z | x > 0) MUST be incremented if only backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
However it does say this:
The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.