←back to thread

Memory Safety in C# vs. Rust

13 points northlondoner | 2 comments | 16 Dec 25 12:55 UTC | HN request time: 0.431s | source

Noticed how C# is underrated. About memory safety in C#. How difficult to introduce multi-paradigm memory safety approach like Rust? Ownership model for example, would it be possible to enforce practice via some-sort of meta framework?
1. exceptione ◴[16 Dec 25 18:19 UTC] No.46292118[source]▶
neonsunset shared an interesting article, but his comment is dead: https://em-tg.github.io/csborrow/

/btw, I am not affiliated with neonsunset, but could people please comment to explain what is wrong instead of downvoting? If there is any substance to a comment and it isn't obviously a misinformation or disinformation one (Paradox of Tolerance), we should have a discussion instead.

On topic: Could F* unlock even more possibilities, like crossing the gap of the heap and the stack in terms of direct access? It has a very powerful type system and it can eject an F* program to F#.

replies(1): >>46293747 #
2. romanhn ◴[16 Dec 25 20:11 UTC] No.46293747[source]▶
Looks like many/most of their comments are dead, probably some account-level action that was taken at some point. Vouched for the comment here to bring it back from the dead.