3 ms·
Yeah in practice the Rust community writes a lot of code that uses experimental features, that need an explicit feature gate and the nightly build of the compil
by remram 4y ago
Yeah in practice the Rust community writes a lot of code that uses experimental features, that need an explicit feature gate and the nightly build of the compiler. This is less common now, but it was huge during earlier development; a lot of the async work only ran on nightly compilers.
If the Rust team refuses to ship the features in stable releases, people are just going to use unstable releases and that will make the experience worse for everyone.
There is no way to artificially restrict features unless you have multiple software in the ecosystem that needs time to update: for C it is the other compilers following the C standard, for Python it is the Python executable on your end- user's machine. The minute rustc updates, Rust developers have little reason not to use the features.
- estebank 4y ago> This is less common now, but it was huge during earlier development; a lot of the async work only ran on nightly compilers. How is this a problem? The crate authors targeting nightly features know full well that they are restricting their pool of users, while at the same time driving the testing and design of nightly features forward. If no one is actually using them, then they are unlikely to get quickly stabilized. > If the Rust team refuses to ship the features in stable releases Can you show a case of refusal to ship a needed feature? > Rust developers have little reason not to use the features. Rust developers of end user applications don't. Crate authors do, if they want to gain wide adoption.
- remram 4y agoI feel like you read my entire comment wrong. Like you didn't read what I replied to, stripped all the "ifs" and arguments, and hyper-focused on points I wasn't trying to make. Surely I wasn't as clear as I thought but this feels so strange.