3 ms·
Having tools to avoid data races don't make it a memory-safe language, unless you strip that phrase of all meaning. The more interesting question is, would it
by morelisp 3y ago
Having tools to avoid data races don't make it a memory-safe language, unless you strip that phrase of all meaning.
The more interesting question is, would it be worth it to be memory-safe? Rust says yes, and puts a lot of work into statically preventing data races at the cost of (at least) some language ergonomics. Java also says yes, but put a lot of work into making data race impacts well-defined, and on this tends to incur cost (runtime and language development time) with unclear benefits towards actually reasoning about the programs with such races.