this post was submitted on 10 Jun 2024
19 points (95.2% liked)
Rust
6009 readers
4 users here now
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Wormhole
Credits
- The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Nightly is for language features of Rust that are still being tested or experimented with. It should only be used by developers who are eager for the latest bleeding edge capabilities and are willing to adapt if those capabilities change or get dropped entirely. Or you might use nightly if you're a good citizen and testing out the experimental capabilities so that you can give feedback on them.
A later version of nightly could potentially change or drop the features of an earlier version of nightly in ways that are not backwards compatible. That's why you might have to specify which version of nightly you need (potentially an older version), if you're building something that depended on nightly features.
Ah, so what I'm seeing is an edge case and not the standard? Does that mean I can reference
standard:2.0
because the only reference I can find is https://rust-lang.github.io/rustup-components-history/aarch64-unknown-linux-gnu.html which is always date and never version number.Thank you BTW!
I'm not familiar enough with what you're trying to do to offer any specific advice. I've spent very little time with writing dockerfiles, and have never needed to set up a Rust toolchain in a dockerfile.
I think the first step is figuring out if nightly is really needed. If there aren't any nightly features needed then the latest stable toolchain should work fine, and worrying about what version of the toolchain to use is a red herring.
Thank you so much. I appreciate you taking the time out of your day to help.