Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rust 1.26 released

blog.rust-lang.org

Post reply on HN
Print view View original

31–40 of 178 posts

Re: Rust 1.26 released

#31

Post by steveklabnik »

pimeys wrote: post #30
kibwen wrote: post #7

So yeah, 1.26 is the most substantial release since 1.0, but there's lots more goodies coming in the pipeline. :) It just so happened that all the initiatives from last year are preparing to land at approximately the same time. For example, coming up next in 1.27 is stable SIMD: https://github.com/rust-lang/rust/pull/49664 (though only for x86/x86_64 at first; more platforms and high-level crossplatform APIs are on t…

The features I'm highly expecting are pinned references and async/await, that will make most of my paid Rust to be so much more readable and maintainable. I know these are coming this year, but any chance they might be already in 1.27? 1.26 has impl Trait, which is one of those things that really makes your life easier as a Rust developer. I've been using beta already with the new API I'm building just to get that fe…

Pin is in nightly, but async/await is not. Both will certainly miss 1.27, and my guess is MAYBE 1.28, probably 1.29.

Re: Rust 1.26 released

#32

Post by neptvn »

steveklabnik wrote: post #2

So, so, so much stuff in this release! The next few are shaping up to be similar. Very exciting times! As always, happy to answer questions, provide context, etc.

Congrats to the Rust team and all contributors! Awesome work!

Is the non-lexical lifetime improvements work locked to a particular release yet?

Also, now that the async/await RFC has been merged, is its implementation in nightly or stable going to be squeezed in for the 2018 roadmap plans?

Re: Rust 1.26 released

#33

Post by steveklabnik »

Promarged wrote: post #29

Congrats on the release! Would the book be updated as new features are added to Rust? I see some useful things being incorporated slowly into the language...

Yes and no. Think of it like release trains; the second edition has left the station, and so isn't being updated directly. It's actually pinned to 1.21; it left the station a while back.

Work on the "2018 edition", which is the next version after "second edition", is just starting. It will be getting updates as new stuff lands, though there may be a bit of lag. In general, docs are going to be a bit weird up to the Rust 2018 release; it's all coming together, but slower at first, faster at the end.

(This means that, as of right this moment, there aren't great docs for impl Trait. I'm working on them right now.)

Re: Rust 1.26 released

#34

Post by steveklabnik »

bpicolo wrote: post #26
steveklabnik wrote: post #25

Earlier quoted context omitted.

Every language I’m aware of has different syntax for inclusive vs exclusive range; making it situational would be quite confusing, I’d imagine.

Definitely agree that having the inclusive syntax makes sense either way (..= was mildly jarring at first but makes complete sense syntactically) - I just mean the exclusive ranges arriving at that compiler error definitely seems unexpected

Ah! Yeah, I mean maybe. At the same time, special cases can make things harder to understand. This would also technically be a breaking change, though probably not changing any realistic programs.

Re: Rust 1.26 released

#35

Post by kibwen »

pimeys wrote: post #30
kibwen wrote: post #7

So yeah, 1.26 is the most substantial release since 1.0, but there's lots more goodies coming in the pipeline. :) It just so happened that all the initiatives from last year are preparing to land at approximately the same time. For example, coming up next in 1.27 is stable SIMD: https://github.com/rust-lang/rust/pull/49664 (though only for x86/x86_64 at first; more platforms and high-level crossplatform APIs are on t…

The features I'm highly expecting are pinned references and async/await, that will make most of my paid Rust to be so much more readable and maintainable. I know these are coming this year, but any chance they might be already in 1.27? 1.26 has impl Trait, which is one of those things that really makes your life easier as a Rust developer. I've been using beta already with the new API I'm building just to get that fe…

The RFC for async/await was actually just accepted two days ago! https://github.com/rust-lang/rfcs/pull/2394#issuecomment-387... :) It's a priority for this year, but it'll be a few months yet; unless something goes unexpectedly wrong, I'd expect it no later than 1.30, releasing on October 25th.

Re: Rust 1.26 released

#37

Post by Rusky »

the_mitsuhiko wrote: post #28
tylerhou wrote: post #16

Earlier quoted context omitted.

I think because returning two different types requires dynamic dispatch when using the returned objects, which requires Box; if the function only returns one type then that type can be determined at runtime and further function calls can be implemented with static dispatch instead.

Rust could generate a bespoke internal proxy type.

That would still require dynamic dispatch of some kind.

Re: Rust 1.26 released

#38

Post by Manishearth »

neptvn wrote: post #32
steveklabnik wrote: post #2

So, so, so much stuff in this release! The next few are shaping up to be similar. Very exciting times! As always, happy to answer questions, provide context, etc.

Congrats to the Rust team and all contributors! Awesome work! Is the non-lexical lifetime improvements work locked to a particular release yet? Also, now that the async/await RFC has been merged, is its implementation in nightly or stable going to be squeezed in for the 2018 roadmap plans?

Yeah, the plan is for async/await to be part of the 2018 edition, but it's going to take some time.

Re: Rust 1.26 released

#39

Post by kibwen »

neptvn wrote: post #32
steveklabnik wrote: post #2

So, so, so much stuff in this release! The next few are shaping up to be similar. Very exciting times! As always, happy to answer questions, provide context, etc.

Congrats to the Rust team and all contributors! Awesome work! Is the non-lexical lifetime improvements work locked to a particular release yet? Also, now that the async/await RFC has been merged, is its implementation in nightly or stable going to be squeezed in for the 2018 roadmap plans?

async/await has been on the 2018 roadmap from the start: https://blog.rust-lang.org/2018/03/12/roadmap.html

As for non-lexical lifetimes, there's lots that's been implemented but much of it is still experimental; follow Niko Matsakis' blog series at http://smallcultfollowing.com/babysteps/blog/2018/04/27/an-a... to stay up to date with what's happening.

Re: Rust 1.26 released

#40

Post by Animats »

steveklabnik wrote: post #25
bpicolo wrote: post #24

> Inclusive ranges are especially useful if you want to iterate over every possible value in a range Out of curiosity, why was the (or an alternative) choice not to make the compiler understand that the 0..256 was not inclusive, and somehow correct the literal value to do what's intended? Would that have been unusually complicated or? Edit: Overall, still an amazing release, this was just the bit I'm curious about :)…

Every language I’m aware of has different syntax for inclusive vs exclusive range; making it situational would be quite confusing, I’d imagine.

Go deliberately left that out.[1] Probably a good decision.

[1] https://groups.google.com/forum/#!msg/golang-nuts/7J8FY07dkW...

Post reply on HN