3 ms·
> with less fear for the situations where you do need to bypass the borrow checker such as with cyclical references in graphs That's a pretty tricky thing to g
by proto_lambda 3y ago
> with less fear for the situations where you do need to bypass the borrow checker such as with cyclical references in graphs
That's a pretty tricky thing to get right, and with the consequence for getting it wrong being UB, at least a little fear is warranted.
- likeabbas 3y ago`compiler_unverifiable` isn't risky enough for you?
- ZephyrBlu 3y agoIt doesn't have the same connotations as `unsafe`.
- likeabbas 3y agoBut it’s the true definition being stated. Unsafe is subjective, compiler unverifiable isn’t
- ZephyrBlu 3y agoSo? This is like applications adding artificial delay to operations so users aren't surprised they complete so quickly. User understanding is more important than definitional correctness.
- likeabbas 3y agoI don’t understand why you want people to be afraid of code though. It’s just code. We don’t need a scary connotation to make people think they should shoot for completely compiler verifiable rust in every line they can write.
- proto_lambda 3y agoUsers who don't even know the meaning of "unsafe" almost definitely shouldn't be writing unsafe code.
- likeabbas 3y agoThat's an elitist mindset
- ZephyrBlu 3y agoIt's a user-friendly mindset.
- likeabbas 3y agoUser-friendly is subjective. I think it would be more user friendly to tell users "hey, this code you're writing can't be verified by the compiler" rather than "hey, this code is unsafe. beware"
- proto_lambda 3y agoWhat it boils down to is "Users who don't even know what a trigger is should be discouraged from handling footguns". Sure, if you don't have the resources to learn about the subject, you might miss out on some fun, but it's much more likely that you'd blow off your foot instead, which would be much less fun.