Improving C# Memory Safety

(devblogs.microsoft.com)

39 points | by soheilpro 1 day ago

2 comments

  • pjmlp 1 day 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.
    • moomin 43 minutes ago
      The Windows team is talking to DevDiv again? Satan's putting on his ice skates right now.
  • superjan 1 hour ago
    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.