Hacker News new | ask | show | jobs
by dontlaugh 397 days ago
That’s likely because p/invoke is quite common.
1 comments
neonsunset 397 days ago
No, that's just the memory model of CLI and the choice made by C#. By default, it emits localsinit flag for methods which indicates that all local variables must be zero-initialized first. On top of that, you can't really access unitialized memory in C# and F# anyway unless you use unsafe. It's a memory safety choice indeed but it has nothing to do with P/Invoke.
link
dontlaugh 397 days ago
The main motivation to use unsafe is p/invoke.

Without unsafe, zero init is not needed.

link
neonsunset 397 days ago
> The main motivation to use unsafe is p/invoke.

This is opposite to the way unsafe (either syntax or known unsafe APIs) is used today.

link
dontlaugh 397 days ago
Explicit use of unsafe is used for things like avoiding allocation, sure.

All use of p/invoke is also unsafe though, even if the keyword isn’t used. And it’s much more common to wrap a C library than to write a buffer pool.

link