2 ms·
Nightly isn't really as unstable as the name implies. Without invoking `#![feature(...)]` flags it's basically functions identically to stable. Sure, occasiona
by gpm 8y ago
Nightly isn't really as unstable as the name implies. Without invoking `#![feature(...)]` flags it's basically functions identically to stable. Sure, occasionally something breaks, then you type `rustup default nightly-<a date a few days ago>` and keep on chugging.
Meanwhile you get access to more and better tools, which has no impact on the stability of your code base but a positive impact on productivity. It enables you to decide to bite the bullet and give up on language stability for new useful features if you want to (which I often do, for nll).
So, what I do is develop on nightly, and make things I want other people to use work on stable.
- jnbiche 8y ago> what I do is develop on nightly, and make things I want other people to use work on stable. What do you do with the stuff you make on nightly? Use it only for yourself? Edit: oh, I think I see: you don't use any new features when you develop on nightly.
- steveklabnik 8y agoSome people use nightly to actually build, but don't turn on any nightly-only features. This means that they get early access to bugfixes and improvements, but don't actually restrict their users to nightly. (This may not be what your parent is talking about, but it is a use-case I've seen before.)
- gpm 8y agoThis is what I'm talking about.