You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Interesting read for C/C++devs. Nothing much in there that I've not come across before but what did catch my eye was a statement that they don't teach much in computer degree courses about the dangers of memory unsafe code. Really? Explains a lot. I would have thought if you are learning C, the memory unsafe aspects of C and how to mitigate those dangers, other than write in Rust, would be a big part of the course.
I've no plans to rewrite nwipe in rust any time soon, although I'm sure that would be an interesting project for somebody. I get the feeling it would littered with the 'unsafe' keyword as by it's nature it has to do some low level hardware related things, but I'm no rust programmer, so what do I know.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Five Eyes - Memory Safe Languages
Interesting read for C/C++devs. Nothing much in there that I've not come across before but what did catch my eye was a statement that they don't teach much in computer degree courses about the dangers of memory unsafe code. Really? Explains a lot. I would have thought if you are learning C, the memory unsafe aspects of C and how to mitigate those dangers, other than write in Rust, would be a big part of the course.
I've no plans to rewrite nwipe in rust any time soon, although I'm sure that would be an interesting project for somebody. I get the feeling it would littered with the 'unsafe' keyword as by it's nature it has to do some low level hardware related things, but I'm no rust programmer, so what do I know.
The-Case-for-Memory-Safe-Roadmaps-508c.pdf
Beta Was this translation helpful? Give feedback.
All reactions