DigiNews

Summary

Microsoft’s .NET team outlines a forthcoming C# memory-safety model (C# 16) that treats unsafe as a compiler-enforced contract rather than a mere context. The model introduces safety documentation, explicit caller obligations, and boundary methods, with project-level opt-in controls and a migration path for runtime libraries. The post includes examples, cross-language comparisons (Rust, Swift), and discusses how these changes will impact code audits and supply-chain safety.