4 ms·
Why should we constrain ourselves to not use the word 'safe' in the context of one of the most privileged portions of code running on a computer? Linus has mad
by monocasa 4y ago
Why should we constrain ourselves to not use the word 'safe' in the context of one of the most privileged portions of code running on a computer?
Linus has made it pretty clear that it's why he's allowing it; it provides something above and beyond other system languages wrt to writing correct code while still working with the kernel's structure and requirements (with a little elbow grease).
- sdfhdhjdw3 4y agoThe reason why is asked "without the word safe" is that on HN rust seems like cargo cult, in the sense that the word "safe" is used as a thought stopping - after all, who is against "safe"? - and so its meaning is never really explained.
- adgjlsfhk1 4y agoThe meaning of "safe" is pretty straightforward. It means that you don't read memory that you have freed, don't read memory that you haven't initialized, and don't read or write memory that you don't own.