this post was submitted on 18 Dec 2023
41 points (97.7% liked)

Rust

5960 readers
2 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
EdTheLegendary@programming.dev
kahnclusions@programming.dev
torcherist@programming.dev
41
The rabbit hole of unsafe Rust bugs – notgull – The world's number one source of notgull (notgull.net)
submitted 10 months ago by snaggen@programming.dev to c/rust@programming.dev
6 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] KiranWells@pawb.social 5 points 10 months ago

I believe you are correct; if the unsafe code can cause undefined behavior if input data is not following a specific contract, then the entire function should be labeled unsafe so the caller knows that.

The other option is to check to make sure the contract is valid, and return an error or panic if it is not. That function would be sound, as no inputs cause undefined behavior.