3 ms·
Don't assume I haven't read it. I read the book. Wrapping unsafe code behind an API doesn't make it go away. It's still unsafe and needs manual checking. Also
by hu3 8y ago
Don't assume I haven't read it. I read the book.
Wrapping unsafe code behind an API doesn't make it go away. It's still unsafe and needs manual checking.
Also wrapping code with hints and annotations of some sort is a thing in numerous PL. It's a given, not a feature and certainly not a bug as you wrongly implied I stated.
TLDR: it's still unsafe as the book and others pointed out.
- clouddrover 8y agoThen you're misrepresenting what the book is saying, which is worse than not having read it. As an argument your position makes no sense. You might as well be arguing that there's no point in programming languages because sometimes you have to write assembly.
- hu3 8y agoSince you replied with a personal attack and added nothing to the discussion: It's still unsafe and if you think otherwise either provide an argument that refutes me, the book and othets on this thread instead of blindly dismissing us as: you're reading it wrong. Your very copy-pasted paragraph from the book stated that's still unsafe and it's left to the programmer to get it right.