To kill memory safety bugs in C code, try the TrapC fork
To kill memory safety bugs in C code, try the TrapC fork
go.theregister.com To kill memory safety bugs in C code, try the TrapC fork
Memory-safe variant is planned for next year
cross-posted from: https://rss.ponder.cat/post/57035
2
comments
There's a lot of bold claims being made. No segfaults, no memory leaks, etc. I'm curious to see how that's implemented.
Also:
it's safer than Rust because it lacks an "unsafe" keyword
lol
3 0 ReplyOh, how many times have I wished for a pointer to just null itself.
This one, depending upon how it gets implemented, should be a really good one.4 0 Reply