Ah, that's interesting, I assume this is the link: https://dropbox.tech/infrastructure/lossless-compression-with-brotli https://dropbox.tech/infrastructure/los

Ah, that's interesting, I assume this is the link: https://dropbox.tech/infrastructure/lossless-compression-with-brotli https://dropbox.tech/infrastructure/lossless-compression-wit... Shows a significant improvement in compression code and some examples of checks that can't be elided. I guess this makes sense because it's pretty much the worst case scenario for bounds check impact. I can still personally say that every time I've blamed rust's bounds checks, I was wrong. EDIT: neither the unsafe flag nor the macro appear to be present in https://github.com/dropbox/rust-brotli/ https://github.com/dropbox/rust-brotli/ anymore today, removed some time in 2017. So it seems they found some other way to deal with it?