5 ms·
I'm very excited at the progress in this release. In particular I'm thrilled at the ongoing focus on ergonomics and overall developer experience, what with the
by kibwen 12y ago
I'm very excited at the progress in this release. In particular I'm thrilled at the ongoing focus on ergonomics and overall developer experience, what with the push for quality documentation (brand-new tutorials, code examples for all library functions, and API stability markers) and the rapid maturation of Cargo. Also, lifetime elision and `where` clauses have done wonders in reducing the horror that has historically plagued Rust function signatures.
There's also been tons of progress toward the last features that are blocking the 1.0 release (http://blog.rust-lang.org/2014/09/15/Rust-1.0.html http://blog.rust-lang.org/2014/09/15/Rust-1.0.html). The long-awaited work on dynamically-sized types is now partially complete, and the only two remaining big hurdles that I can think of are closure reform and trait coherence reform. Onward to stability!
- untothebreach 12y agoexcuse my ignorance, but what exactly does 'lifetime elision' mean?
- mbrubeck 12y agoIn cases where a function's input and output have the same lifetime, the lifetime is now inferred. So instead of this: fn f<'a>(x: &'a SomeType) -> &'a OtherType you can now write this: fn f(x: &SomeType) -> &OtherType Same meaning, just more concise syntax.
- untothebreach 12y agoah, got it. thanks!
- thomasahle 12y agoUhm, what if I didn't want `&OtherType` to have the same lifetime? Would I then write: fn f<'a>(x: &'a SomeType) -> &'b OtherType ?
- kimundi 12y agoYes, though this particular code would not compile because one of the lifetimes is not declared.
- kibwen 12y agoThat would be illegal, because it only makes sense to return a reference when that reference is somehow linked to the lifetime of an input parameter. (Or when it has a lifetime of `static`, which means the referent is stored in static memory and thus is alive for the whole program.)
- thristian 12y agoWhat if you're looking up the input in a temporary cache of some kind, and returning a reference to the cached value? The lifetime of the input and output would not be related in that scenario, but the output would not necessarily be 'static (maybe you build a cache, run some functions, tear it all down, then build a new cache with different values and do it all again).
- steveklabnik 12y agoThe lifetime would be matched to the lifetime of the cache, which has to be referred to somehow.
- thomasahle 12y agoAh cool, I still have a lot to learn about rust :)
- TD-Linux 12y agoYou wouldn't use a reference generally, if you're thinking of creating a new independent object you'd just return that. This is for cases when your return object is a reference into your argument, for example
- steveklabnik 12y agoPart of Rust's ownership system are 'lifetimes.' Without getting into the details, they're an annotation you occasionally add to code in certain situations. Like these two: fn get_mut<'a>(&'a mut self) -> &'a mut T; fn print<'a>(s: &'a str); The 'a parts are the lifetime annotations. We used to have a single inference rule for when you didn't need to write the annotation. With RFC 39[1], we added two more. These two extra inference rules removed 87% of the existing annotations, giving you this instead: fn get_mut(&mut self) -> &mut T; fn print(s: &str); This is a pretty huge readability win. 1: https://github.com/rust-lang/rfcs/blob/master/active/0039-lifetime-elision.md https://github.com/rust-lang/rfcs/blob/master/active/0039-li...
- untothebreach 12y agooh ok, thanks. i knew what lifetimes were, but was confused by the 'elision.' Apparently I didn't connect 'elision' with 'elide.' So, new vocab word for today :)
- haberman 12y agoWhat kind of cases do you still need to write explicit lifetimes?
- steveklabnik 12y agoI actually haven't had to since elision was implemented, so I can't give you a good rule of thumb from experience. Here's an overview of how the rules applied to the standard library at the time they were implemented, which is where the percentage came from: https://gist.github.com/aturon/da49a6d00099fdb0e861 https://gist.github.com/aturon/da49a6d00099fdb0e861
- xKingfisher 12y agoThe most common case I have run into is storing a reference inside another data structure.
- kibwen 12y agoBasically, after working with lifetimes for so long we realized that a great many functions that take lifetime parameters follow a similar and straightforward pattern. As of this release, we now allow you to omit lifetime parameters entirely for functions that follow this pattern, which is likely the vast majority of functions in your code that previously required such annotations. The detailed release notes have a more, er, detailed explanation: https://github.com/rust-lang/rust/wiki/Doc-detailed-release-notes https://github.com/rust-lang/rust/wiki/Doc-detailed-release-...
- yen223 12y agoThis is a great change. But to clarify, functions which take 2 or more reference inputs won't benefit from this, since the compiler can't determine which lifetime parameter to use, right? Edit: Never mind, I RTFM. Turns out it can't benefit.
- saosebastiao 12y agoIt has come a long way since I first started using it (0.6 era). Congratulations on the release! I look forward to a future world where I can use it (via Servo) in Firefox, as well as in my Constraint Solver engine, which I hope to reveal for the 2015 Minizinc Challenge.
- nnethercote 12y agoMiniZinc! There's a blast from the past... I wrote most of the first few versions of the specification and much of the initial implementation. Good to hear it's still being useful.
- Ygg2 12y agoIs there like a what's new in Firefox but for Rust?
- frewsxcv 12y agoYes. Click on the link and scroll down.
- blinkingled 12y agoDoes the RFC230 (https://github.com/rust-lang/rfcs/pull/230 https://github.com/rust-lang/rfcs/pull/230) removal of green threads give me out of box 1:1 threading or just that std::io uses native threads and the rest has to use green threads only now as an additional outside dependency? Kinda confused given I don't follow Rust all that much. Really odd that they went with M:N model - if the OS is fast at creating/destroying threads 1:1 is the best model for vast majority of apps.
- wycats 12y agoThe default is 1:1 threads. If you use `spawn` in Rust, you get a native thread.
- blinkingled 12y agoOh, it is? I must be reading some old docs and mailing list discussions. That's great to hear. Thanks for the clarification!
- steveklabnik 12y agoIt's changed a number of times. First it was M:N, then 1:1 was added, then 1:1 was made the default, now M:N is getting removed.
- sitkack 12y agoDoes anything preclude M:N threading in a library? It is really useful in quite a number of scenarios.
- kibwen 12y agoI believe the goal is for there to be an officially-supported green threading library, yes.
- steveklabnik 12y agoThe existing libgreen will be moved out to a Cargo library. You just won't be able to seamlessly switch between the two like you did before, you'll have to explicitly use the green threading API instead.
- pkulak 12y agoNoticeably absent is a really good HTTP library.