*sigh*
Unsafe code in your be dependencies does not mean the code itself is unsafe. All it means is that there is a contract you need to enforce when using it. Literally all of your Rust code is built on it. If you don't want unsafe go make code that never has side effects.
Conversation
I really am coming to the side where thinking unsafe was the wrong word choice. It gives the wrong idea as if it's something that should be avoided, rather than an inherent part of doing anything interesting with a computer. It's the guts of any abstraction.
2
8
Replying to
I would have gone with ‘trusted’ for the blocks, but kept ‘unsafe’ on methods.
Very same - up until about a week ago, by when the small seed of discontent that is "but `trusted` sounds like a positive thing!" had grown from "but that's not really an issue" to "...actually, I'm not satisfied with this, and want a better option". (Took over a year.)
1
2
Show replies
I was struggling for a good word but then I saw “trusted”. That’s such a better way of putting it!