News for hackers. Stuff that matters.
Re:Trying Rust for web services by gmfawcett on Thursday October 01, 2015 @02:26PM (#10313414)
"RAII" seems to cover it nicely, and extends beyond memory management to other resources. Admittedly it's not a very friendly term for non-C++ programmers.

What's this non-lexical borrowing idea you mentioned in your other comment? (I can't reply there for some reason.) Is there an RFC for that?

Re:Trying Rust for web services by steveklabnik on Thursday October 01, 2015 @02:40PM (#10313546)
The relevant search terms are "SEME regions" and "non-lexical borrows". The tracking issue is here: https://github.com/rust-lang/rfcs/issues/811 and https://github.com/rust-lang/rust/issues/6393 is the older issue it superseded, with examples.

There hasn't been an RFC yet, because we're in the middle of a large amount of compiler internals work (HIR/MIR), which will make overall analysis easier, including these two features.

> (I can't reply there for some reason.)

HN limits responses based on the depth of the comment tree and the length of time since the comment was posted, to discourage flamewars, you can always click on a comment link directly to kind of bypass that though.

Re:Trying Rust for web services by gmfawcett on Thursday October 01, 2015 @03:17PM (#10313871)
Thanks for the issue link (and for the comment-tree depth hint!).
Re:Trying Rust for web services by acconsta on Thursday October 01, 2015 @03:29PM (#10314000)
Scope-bound resource management (SBRM) is clearer than RAII, I think.