Improving C# Memory Safety
devblogs.microsoft.com70 points by soheilpro 2 days ago
70 points by soheilpro 2 days ago
Most likely a side effect related to Windows team finally giving some C# love, instead of COM and C++, given the comparisons between C# 16 with Rust and Swift in a few article sections.
The Windows team is talking to DevDiv again? Satan's putting on his ice skates right now.
One can only hope.
C++/WinRT is in maintenance, and you will notice the WinUI 3.0 does most of their demos, and gallery with C#.
What you can do in C# today is convert any unsafe pointer to Span whenever you get your hands on it, and pass around slices. You can still drop down to ‘fixed’ when it turns out you need it for performance.