Re:Don’t assume that safety comes for free: a Swift case study
by pjmlp on Tuesday December 06, 2016 @02:42PM
(#13117640)
> How do languages which aim to replace C (such as Rust) deal with this issue?
Just like languages older than C did, by providing the option to explicitly request to disable safety checks.
For example in ESPOL and NEWP (1961), running unsafe modules requires admin permission, user code cannot make use of unsafe. Something like setuid in UNIX.
You don't need 100% unsafe code, rather write it in a safe way, profile it, and then only on the sections that really matter you might turn those checks off, after trying everything else to optimize it.
Just like languages older than C did, by providing the option to explicitly request to disable safety checks.
For example in ESPOL and NEWP (1961), running unsafe modules requires admin permission, user code cannot make use of unsafe. Something like setuid in UNIX.
You don't need 100% unsafe code, rather write it in a safe way, profile it, and then only on the sections that really matter you might turn those checks off, after trying everything else to optimize it.