undefined | Better HN

0 pointsclouddrover7y ago0 comments

I think you need to read on a bit further. The very next section after the sentence you quoted is:

"We need to wrap this struct up into a higher-layer API that is safe for our users to call. As the driver author, we manually verify the unsafe code is correct, and then present a safe API for our users so they don't have to worry about it (provided they trust us to get it right!)."

Rust lets you write clearly defined unsafe code blocks. It's not a bug, it's a feature:

https://doc.rust-lang.org/book/ch19-01-unsafe-rust.html

https://doc.rust-lang.org/nomicon/index.html

It's worth reading through the whole Embedded Rust book even if you won't be implementing such software. It's interesting.

0 comments

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

clouddroverOP7y ago

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

hu37y ago

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

j / k navigate · click thread line to collapse

0 comments

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

clouddroverOP7y ago

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

hu37y ago

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

j / k navigate · click thread line to collapse