Rust's 2018 roadmap
blog.rust-lang.org
Rust's 2018 roadmap
1–10 of 253 posts
Re: Rust's 2018 roadmap
#2Lots of great stuff coming this year! As always, happy to answer any questions.
Re: Rust's 2018 roadmap
#3You may have noticed a subtle change: what was previously called “epochs” is now “editions.” Lots of great stuff coming this year! As always, happy to answer any questions.
Re: Rust's 2018 roadmap
#4I'm interested in seeing how Rust and Go will compare in the future of the web.
Who will win? ;)
Re: Rust's 2018 roadmap
#5Re: Rust's 2018 roadmap
#6Go is making a large push to wasm as well. There is a branch/fork with a near complete wasm Go compiler. I'm interested in seeing how Rust and Go will compare in the future of the web. Who will win? ;)
Re: Rust's 2018 roadmap
#7You may have noticed a subtle change: what was previously called “epochs” is now “editions.” Lots of great stuff coming this year! As always, happy to answer any questions.
What happened to "era"?!
We expect most people to say "Rust 2018" and not use any of these terms; we still need one to be the key in Cargo.toml and the flag to the compiler, so we couldn't just use nothing.
Re: Rust's 2018 roadmap
#8Go is making a large push to wasm as well. There is a branch/fork with a near complete wasm Go compiler. I'm interested in seeing how Rust and Go will compare in the future of the web. Who will win? ;)
Do they ship a GC with every webpage then or am I misunderstanding how it works?
Re: Rust's 2018 roadmap
#9Go is making a large push to wasm as well. There is a branch/fork with a near complete wasm Go compiler. I'm interested in seeing how Rust and Go will compare in the future of the web. Who will win? ;)
Re: Rust's 2018 roadmap
#10Any notes on const generics e.g.`Array[T, N]`?