4 ms·

> which we know you are using for your project because we gated all the features behind it I don't think that's really fair, or at least hasn't been true for a

> which we know you are using for your project because we gated all the features behind it I don't think that's really fair, or at least hasn't been true for a long time now. Use of the stable channel far exceeds use of nightly according to all the surveys. At my company we've always stuck to the stable channel, and even in my own personal projects where I have no need for stability, I don't remember the last time I used a nightly feature, simply because I haven't found the need to... I don't believe there are many cases left where you're forced to use nightly: most of the cases where people are using it is because there's a "nice to have" feature, not because that feature is actually essential. Even rocket, which was famed for using a ton of nightly features, now works on stable Rust.

vlovich123 6y ago
Anyone doing OS development is still on nightly last I checked but aside from that stable has the features most people need.
- rnestler 6y ago
  I'm curios which features OS development need from nightly. Maybe inline assembly? I've been doing some bare metal embedded projects in Rust and didn't need nightly for quite some time.
  - monocasa 6y ago
    I use the following in my kernel project: asm, const_fn, const_generics, exclusive_range_pattern, global_asm, panic_info_message, start, untagged_unions. Of those, I could get away with just global_asm, start, and const_generics if I had to, but the others certainly make my life easier in a kernel space without an allocator. I'll be the first to admit that some of those are "I'm just going to embrace nightly if I'm stuck on it anyway".
pjmlp 6y ago
If you want to profile your builds or compiler, nightly is still required.
- kibwen 6y ago
  That's beside the point of what's being discussed here. The concern is that using unstable feature flags in your code, which only work on nightly, allows your code to be broken by compiler upgrades. But using nightly doesn't magically introduce unstable feature flags. There's no compability hazard from merely compiling a compiles-on-stable codebase with a nightly compiler for whatever reason.
  - pjmlp 6y ago
    Sorry if I thought tooling capabilities were a relevant compiler feature then.

vlovich123 6y ago

Anyone doing OS development is still on nightly last I checked but aside from that stable has the features most people need.

rnestler 6y ago
I'm curios which features OS development need from nightly. Maybe inline assembly? I've been doing some bare metal embedded projects in Rust and didn't need nightly for quite some time.
- monocasa 6y ago
  I use the following in my kernel project: asm, const_fn, const_generics, exclusive_range_pattern, global_asm, panic_info_message, start, untagged_unions. Of those, I could get away with just global_asm, start, and const_generics if I had to, but the others certainly make my life easier in a kernel space without an allocator. I'll be the first to admit that some of those are "I'm just going to embrace nightly if I'm stuck on it anyway".

pjmlp 6y ago

If you want to profile your builds or compiler, nightly is still required.

kibwen 6y ago
That's beside the point of what's being discussed here. The concern is that using unstable feature flags in your code, which only work on nightly, allows your code to be broken by compiler upgrades. But using nightly doesn't magically introduce unstable feature flags. There's no compability hazard from merely compiling a compiles-on-stable codebase with a nightly compiler for whatever reason.
- pjmlp 6y ago
  Sorry if I thought tooling capabilities were a relevant compiler feature then.