4 ms·

Rocket still requires nightly. Rust folks should stop normalizing the use of nightly. Rust was "stabilized" almost 9 (edit 5,5 actually) years ago!

jeltz 6y ago
Do you have any idea why that is? I am pretty sure procedural macros in an expression context landed in stable 1 or 2 releases ago.
- mathstuf 6y ago
  I believe they are waiting for releases of dependencies to not declare feature requirements. There's an issue linked in this subthread already for tracking it.
  - steveklabnik 6y ago
    That is already done, and master builds on stable. They haven't cut a release yet because there's more they want in the release than just "whatever is on HEAD when we compile on stable."
- nicoburns 6y ago
  Rocket's development process is quite slow, and they haven't but out a release since then.
bschwindHN 6y ago
Wasn't Rust "stabilized" with its 1.0 release in 2015?
- Ygg2 6y ago
  Yes. But meta programming facilities aren't stabilized for obvious reasons (it ossifies the current implementation).
  - paavohtl 6y ago
    Most meta programming facilities are stabilized, most importantly procedural macros.
    - Ygg2 6y ago
      I'm not up to date with Rust tbh. Last time I checked Rocket used proc macros which were nightly only. But maybe there is some other issue.
      - paavohtl 6y ago
        Most procedural macros were stabilised in 2018, but some smaller features related to them were stabilised later. Rocket also used a ton of other nightly features beyond metaprogramming, which have either been stabilised by the compiler or replaced with stable solutions by Rocket.
simias 6y ago
I agree regarding the use of nightly Rust but fortunately it shouldn't be too long until a stable-compatible Rocket is released: https://github.com/SergioBenitez/Rocket/issues/19 https://github.com/SergioBenitez/Rocket/issues/19
paavohtl 6y ago
Technically speaking, stable Rocket requires nightly Rust, but nightly (master) Rocket runs on stable Rust. The compiler has finally stabilised all the necessary features for Rocket 1.0, it's just up to Rocket to finish their next release.

jeltz 6y ago

Do you have any idea why that is? I am pretty sure procedural macros in an expression context landed in stable 1 or 2 releases ago.

mathstuf 6y ago
I believe they are waiting for releases of dependencies to not declare feature requirements. There's an issue linked in this subthread already for tracking it.
- steveklabnik 6y ago
  That is already done, and master builds on stable. They haven't cut a release yet because there's more they want in the release than just "whatever is on HEAD when we compile on stable."
nicoburns 6y ago
Rocket's development process is quite slow, and they haven't but out a release since then.

bschwindHN 6y ago

Wasn't Rust "stabilized" with its 1.0 release in 2015?

Ygg2 6y ago
Yes. But meta programming facilities aren't stabilized for obvious reasons (it ossifies the current implementation).
- paavohtl 6y ago
  Most meta programming facilities are stabilized, most importantly procedural macros.
  - Ygg2 6y ago
    I'm not up to date with Rust tbh. Last time I checked Rocket used proc macros which were nightly only. But maybe there is some other issue.
    - paavohtl 6y ago
      Most procedural macros were stabilised in 2018, but some smaller features related to them were stabilised later. Rocket also used a ton of other nightly features beyond metaprogramming, which have either been stabilised by the compiler or replaced with stable solutions by Rocket.

simias 6y ago

I agree regarding the use of nightly Rust but fortunately it shouldn't be too long until a stable-compatible Rocket is released: https://github.com/SergioBenitez/Rocket/issues/19 https://github.com/SergioBenitez/Rocket/issues/19

paavohtl 6y ago

Technically speaking, stable Rocket requires nightly Rust, but nightly (master) Rocket runs on stable Rust. The compiler has finally stabilised all the necessary features for Rocket 1.0, it's just up to Rocket to finish their next release.