Hacker News Reader

Seeing 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.

I don't know why Rust gets "runtime" and Nim gets "compile time" for type confusion?

yes, 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)

Thanks! I'd love to see a Dlang BetterC column too

Here's a version with D included:

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.

I guess rust should say "wraps" for integer overflow as well, as that's what it does in default release compile.