3 ms·
And here is the table with Nim added; though potentially many GC'd languages would be similar to Nim: https://uploads.peterme.net/nimsafe.html https://uploads.
by dleslie 4y ago
And here is the table with Nim added; though potentially many GC'd languages would be similar to Nim:
https://uploads.peterme.net/nimsafe.html https://uploads.peterme.net/nimsafe.html
Edit: noteworthy addendum: the ARC/ORC features have been released, so the footnote is now moot.
- jewpfko 4y agoThanks! I'd love to see a Dlang BetterC column too
- Snarwin 4y agoHere's a version with D included: https://gist.github.com/pbackus/0e9c9d0c83cd7d3a46365c054129c554 https://gist.github.com/pbackus/0e9c9d0c83cd7d3a46365c054129... The only difference in BetterC is that you lose access to the GC, so you have to use RC if you want safe heap allocation.
- kzrdude 4y agoI guess rust should say "wraps" for integer overflow as well, as that's what it does in default release compile.
- 3a2d29 4y agoSeeing Nim danger made me think, shouldn’t rust unsafe be added? Seems inaccurate to display rust as safe and not include what actually allows memory bugs to be found in public crates.
- IshKebab 4y agoI don't know why Rust gets "runtime" and Nim gets "compile time" for type confusion?
- shirleyquirk 4y agoyes, for tagged unions specifically, (which the linked post refers to for that row) Nim raises an exception at runtime when trying to access the wrong field, (or trying to change the discriminant)