Regulating our MSRV about opentelemetry-rust HOT 5 OPEN

I think our general idea is to keep the MSRV as low as possible. Could you elaborate on what benifit of using a certified compiler? I'd image most of our users use vanilla Rust compiler

from opentelemetry-rust.

Yes i would agree that we don't want to bump the compiler if we do the have to, but that the ceiling for that should be lower than just 3 behind latest stable.

The reason for using the certified compiler is for government regulation purposes, the most cited example is things like automotive. C and C++ follow compliance of a number of ISO standards. The goal for these is have predictable behavior from a spec. Currently the rust compiler itself doesn't have one (yet) but there's active work.

A blog post from late last year talks about some of it https://blog.rust-lang.org/inside-rust/2023/11/15/spec-vision.html
Ferrocene blog https://ferrous-systems.com/blog/officially-qualified-ferrocene/

from opentelemetry-rust.

Note that env_logger is only used in examples, so keeping an older version around really doesn't matter.

In many projects I have my MSRV CI jobs set to run cargo check --lib to avoid dev-dependencies like this, but unfortunately that doesn't work for this case because env_logger adopted some Cargo manifest options that break on older Cargo whether the dependency is actually pulled in or not.

from opentelemetry-rust.

Ah so in this case we can also avoid this conflict for env_logger at least by not caring about the examples.

from opentelemetry-rust.

Yup!

from opentelemetry-rust.