3 ms·

Don't understand why this bug deserves thread on HN.

• zmanian 12y ago
  Safe Fork-join concurrency which the entire stack frame is available to the new thread is a very sexy Rust feature. It's unfortunate that this feature won't make into 1.0. It was one of the more exciting concurrency features that looked like it would be in 1.0 until this bug. See Steve's last example here. http://blog.rust-lang.org/2015/04/10/Fearless-Concurrency.html http://blog.rust-lang.org/2015/04/10/Fearless-Concurrency.ht...
  • CarlColglazier 12y ago
    Since a new minor release is expected to come out every six weeks, it is possible that this will be added even after 1.0 at some point in the near future.
  • steveklabnik 12y ago
    That post was written by Aauron Turon, not me. Though I have been talking about scoped threads a lot lately :)
• mtanski 12y ago
  Up votes by people who don't really buy all the Rust marketing about safety of the language, at least how it's gone about. Personally speaking, and looking others threads on /r/rust, there is a fair amount of frustration when certain things don't work expected due to borrow checker (lifetimes, lexical scoping). So when people who try Rust get a fair amount of smugness about safety when working with it... they will upvote stories where safety has been proved unsound in Rust.
  • Rusky 12y ago
    Except Rust-the-language hasn't been proved unsound. Rust's standard library has been found to introduce unsoundness through the incorrect use of `unsafe` blocks. `thread::scoped`'s interface just has to be tweaked somehow, not removed.