> I know it shouldn't be a big deal but it "feels dirty" and perhaps I should just view nightly as any other language's "stable". There are two uses for nightl

> I know it shouldn't be a big deal but it "feels dirty" and perhaps I should just view nightly as any other language's "stable". There are two uses for nightly: 1. Access to unreleased features. I think I'm down to just needing this for associated_type_defaults (rfc here: https://github.com/rust-lang/rfcs/pull/2532/files https://github.com/rust-lang/rfcs/pull/2532/files). 2. Nightly allows passing extra compiler flags, which is occasionally useful for debugging things like macro expansion. Personally I've found that nightly is pretty solid and I do tend to use it more than stable, but I certainly would not consider it dirty in itself. Furthermore if you're looking at a tutorial or a book the features it relies upon may have gotten into the stable build.