Conversation
Co-authored-by: Jan Kotas <jkotas@microsoft.com>
Co-authored-by: Jan Kotas <jkotas@microsoft.com>
|
@jkotas anything else here from our side? |
|
This needs to be reviewed and signed off by the doc maintainers before merging. It looks good to me otherwise. |
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
2) Replace ```cs with ```csharp 3) Add links to .NET Memory Model
|
@gewarren thank you so much for the corrections! I learned a lot 🙂 I believe, I've addressed all of your requests. |
gewarren
left a comment
There was a problem hiding this comment.
A few xref fixes. I'll commit these.
|
@gewarren ah, thanks, I already fixed them locally (just pushed) via that extension that you recommended |
Nice, that was my hackathon project last year :) |
Awesome! It does look handy. Regarding the PR, who typically merges the PRs? |
Me or one of the other content devs (or you if you have write perms). I'll merge it now. Thanks for adding this doc! |
|
Thanks much! |
|
Here's the live link for anyone like me who was looking for it |
Summary
The document contains best practices when dealing with Unsafe code in .NET (focusing on C#), a set of common unreliable patterns and how to avoid them. Some background on why we do this is described here: dotnet/designs#341
We were using https://learn.microsoft.com/en-us/dotnet/standard/native-interop/best-practices as an inspiration for this doc.
cc @jkotas @richlander
Internal previews