Microsoft plans memory safety improvements for C# inspired by Rust, without dropping automatic memory management
By
Tim Anderson
Master baker tier. Every paragraph earns its place on the tray.
Summary
Microsoft's .NET team is planning to improve memory safety in C# by introducing a new model and redefining the 'unsafe' keyword, drawing inspiration from Rust's safety features while maintaining automatic memory management. The goal is to make C# a language known for type- and memory-safety enforcement, without forcing developers to give up the convenience of garbage collection.
Key quotes
· 2 pulledWe envision a future where C# is among a set of languages chosen and noted for the type- and memory-safety enforcement.
Many C# developers never use unsafe, but it has been part of the language from its first release.
You might also wanna read
Building a Rust-Style Static Analyzer for C++ to Prevent Memory Safety Issues
A systems researcher with 15 years of C++ experience describes building a Rust-style static analyzer for C++ called 'rusty-cpp' to address p
Google's Android Security Strategy: Memory Safety and Rust Implementation
Google's Android team discusses their memory safety strategy focusing on vulnerability prevention through programming language choices, spec
Exploring Rust and C Memory Interoperability: Risks and Crash Analysis
The article explores the complexities and dangers of memory interoperability between Rust and C, particularly when using different allocator
Safe C++ Proposal Discontinued After One Year
The Safe C++ proposal, which aimed to add a safe subset to C++ with memory safety, type safety, and thread safety guarantees similar to Rust
Understanding Memory Safety: Addressing Skepticism in Software Development
This article addresses skepticism around memory safety in software development, explaining why memory safety matters despite being a frequen
Eurydice: A Rust to C Compiler for Legacy System Integration
The article discusses Eurydice, a Rust to C compiler, exploring the surprising interest in compiling Rust code to C despite Rust's memory sa
