News for hackers. Stuff that matters.
Re:Formally Verifying Rust's Opaque Types by ArrayBoundCheck on Monday August 01, 2022 @12:03PM (#32308043)
> automatically-placed bounds checks on array accesses

That's exactly why I get annoyed. How will it be fast if it branches on every access

> where the compiler could 'prove'

The compiler doesn't prove shit. It lets the optimizer do it. It's extremely easy to fool the optimizer

> there any 'systems programming' languages

The ones that don't make false claims (so not v or rust) and don't insert code I don't want

Re:Formally Verifying Rust's Opaque Types by throwaway17_17 on Monday August 01, 2022 @12:10PM (#32308175)
Your objection to saying my saying "the compiler could 'prove'" is one of the reasons I put the quotes around prove. Also, thanks for answering, I didn't want my question to seem like baiting or trying to start a string of downvotes, etc. I am honestly interested developer stances on languages, for whatever reason those stances exist.