News for hackers. Stuff that matters.
Re:Concurrency is not Parallelism (it's better) - A talk by ... by Peaker on Friday April 13, 2012 @04:57PM (#3838824)
This sounds like runtime safety, not compile-time safety. Otherwise, how can you avoid aliasing that modifies the object for which you lost ownership?

Immutable state gives you compile-time-safety. I think when people say "shared mutable state is unsafe", at least some of them are referring to compile-time safety. If it compiles, these kinds of concurrency-related bugs are impossible.

Re:Concurrency is not Parallelism (it's better) - A talk by ... by wmf on Friday April 13, 2012 @06:10PM (#3839070)
At least in Rust, unique pointers should be guaranteed by the compiler so when you pass one to another thread you know there's no aliasing.
Re:Concurrency is not Parallelism (it's better) - A talk by ... by riffraff on Saturday April 14, 2012 @03:31AM (#3840198)
AFAIR kilim guarantees statically checked safety, exactly because "messages" that can be sent across actor borders have guaranteed properties of being aliaseable^mutable.