The article is co-authored by Ralf Jung, a prominent postdoctoral researcher in the 'Foundations of Programming' research group at the Max Planck Institute for Software Systems. This article from April's issue of Communications of the ACM provides an overview of Rust and investigates its safety claims. The key challenge in verifying Rust's safety claims is accounting for the interaction between its safe and unsafe code. In its unsafe mode (via use of the "unsafe" block), in which some of its APIs are written, it allows the use of potentially unsafe C-style features.
It also prevents "data races" which is unsynchronized access to shared memory. In its default, safe mode, Rust prevents memory errors, such as "use-after-free" errors. Slashdot reader Beeftopia writes: Rust has two modes: its default, safe mode, and an unsafe mode.
0 kommentar(er)
