![]() In doing so, he also successfully addressed a special aspect of the programming language: "The so-called 'type safety' goes hand in hand with the fact that Rust imposes restrictions on the programmer and does not allow everything that the programmer wants to do. "We were able to verify the safety of Rust's type system and thus show how Rust automatically and reliably prevents entire classes of programming errors," says Ralf Jung. In his dissertation, Ralf Jung now provides the first formal proof that the safety promises of Rust actually hold. And (spoiler alert) Jung has just received one of two 'Honorable Mentions' for the 'Dissertation Award' of the 'Association for Computing Machinery' (ACM), reports a nonprofit site operated by the American Association for the Advancement of Science: 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |