4 ms·
Why "cargo init" instead of "cargo new"? Also, wondering when Rocket will be usable without nightly. That makes me concerned that it is not stable enough.
by bcheung 7y ago
Why "cargo init" instead of "cargo new"?
Also, wondering when Rocket will be usable without nightly. That makes me concerned that it is not stable enough.
- status_quo69 7y agoI've used it for 6 months on the async branch and the master branch and master was incredibly stable. Async is less so because it's a large scale effort to try and convert over the entire API with minimal breakage(apart from fairings/middlewares). You can pin to a specific stable nightly if you're needing extra sanity, although CI makes this hard with the nightly docker images. There's a tracking issue for proc_macro_hygine here: https://github.com/rust-lang/rust/issues/54727 https://github.com/rust-lang/rust/issues/54727 Looks like the last feature is almost stable!
- xena 7y agoI use `cargo init` because I'm used to creating project folders myself.
- nicoburns 7y agoAsync and stable support are both coming soon. I'd estimate within 3-6 months.
- steveklabnik 7y agoRocket uses three nightly features: * proc_macro_hygiene - this feature lets you call procedural macros in more places than you can today. https://github.com/rust-lang/rust/issues/54727#issuecomment-580647446 https://github.com/rust-lang/rust/issues/54727#issuecomment-... might be a bit too in-the-weeds, but the TL;DR is that there seems to be a path forward for stabilizing what Rocket needs in a near-ish timeframe. * proc_macro_diagnostics and proc_macro_span: these purely give Rocket better error messages in some situations. With the first thing stabilized, this could be dropped to get things compiling fully on stable, though diagnostics would regress from nightly. In general, these last bits of things Rocket needs aren't changing a whole lot.