On: $20K Bounty Offered for Optimizing Rust Code in Rav1d AV1 Decoder

[gafferongames]

I think you're taking the term "safety" in rust a bit too literally. It's got bounds checking in it man. That's all. You can also write totally safe programs in C, or if you really want to be serious about it, write the program in F and use formal verification like this crypto library does: https://github.com/hacl-star/hacl-star

[viraptor → gafferongames]

> It's got bounds checking in it man. That's all.

It's got bounds checking, lifetimes, shared access checks, enforced synchronisation, serious typed enums (not enforced but still helpful), explicit overflow behaviour control, memory allocation management, etc. etc. to help with safety. Far from "that's all".

> You can also write totally safe programs in C,

No you can't beyond trivial levels in practice. Even super human exceptions like DJB made mistakes and statistically nobody here is even close to DJB.

> use formal verification like this crypto library does

"Beware of bugs in the above code; I have only proved it correct, not tried it." -D.Knuth (That is - you can make mistakes in the spec too - see how many issues the verified sel4 had https://github.com/seL4/seL4/blob/master/CHANGES.md )

[imtringued → gafferongames]

If you are willing to use formal verification you can just turn off the bound checks in production so I don't get your point.

Also, dismissing bounds checking as "just bounds checking" shows how delusional you are.