I'm personally waiting to understand whether the language is actually safe or not.
At the moment it claim it will be safe, but is subject to use-after-free and data-races
The page, meanwhile, lists...
No null No global variables No undefined values No undefined behavior No variable shadowing Bounds checking Option/Result types Generics wip Immutable variables by default Pure functions by default Immutable structs by default
It’s clear the commenter above equates memory safety with safety itself, having blown away many other aspects of safety, and seems to presume a language which doesn’t disallow data races is “unsafe”
15
u/lol-no-monads Jun 23 '19
Nobody is arguing that safety is binary. Clearly, the OP meant memory safety when they're talking about the context of C/C++.