News for hackers. Stuff that matters.
Re:D as a Better C by steveklabnik on Wednesday August 23, 2017 @02:58PM (#15084142)
Rust's major goals this year are around learnability and productivity; maybe come check it out again someday :)
Re:D as a Better C by theprotocol on Wednesday August 23, 2017 @03:47PM (#15084477)
Could you point to any materials (e.g. blog post, roadmap document...) that deal with this? Thanks.
Re:D as a Better C by steveklabnik on Wednesday August 23, 2017 @04:06PM (#15084589)
https://blog.rust-lang.org/2017/07/05/Rust-Roadmap-Update.ht... is our "the year is half over" update, and has a link to the overall goals right at the top.
Re:D as a Better C by theprotocol on Wednesday August 23, 2017 @05:14PM (#15085248)
Awesome, thanks!
Re:D as a Better C by OoooooooO on Wednesday August 23, 2017 @06:27PM (#15085741)
Inferred lifetimes? A man can hope :).
Re:D as a Better C by dbaupp on Wednesday August 23, 2017 @08:17PM (#15086499)
Inferring lifetimes from the implementation of a function won't happen for the same reason that inferring types won't happen: it is really nice for the signature of a function to not automatically be changed if the body is changed, instead programmers should be told when they might be breaking their users.

However, the compiler could (and did, I believe) run inference and suggest a fix that the programmer can explicitly include.

Re:D as a Better C by steveklabnik on Wednesday August 23, 2017 @06:51PM (#15085886)
If it were always possible to infer all lifetimes, we'd do it. Unfortunately that's not the case.

There are a number of RFCs in the pipeline to help with lifetimes, including more elision. In no particular order:

https://github.com/rust-lang/rfcs/pull/2115

https://github.com/rust-lang/rfcs/pull/2094

https://github.com/rust-lang/rfcs/pull/2093