You seem to have it backwards. The goal is to discourage future manifesto-publishers from murdering. Just as school shootings used to be a good way to get your face on TV, murder is a good way to market your manifesto.…
This manifesto is just the expression of one man's fringe political views. There is a lot of rubbish in it. For example, he spends pages insinuating that leftism is rooted in masochistic, self-hating, chauvinistic…
If you'd used 50.. instead of _, Rust would've caught this error for you. ;) https://play.rust-lang.org/?version=nightly&mode=release&edi...
Nitpick: I'm pretty sure that "11..50" should be a "10..50".
Does it still elide the bounds check if you replace the first three lines with assert_eq!(xs.len(), ys.len()); ?
What would a browser even need a backend for? The only valid use that I can think of is Google's Safe Browsing list, but if ad blocking can be implemented totally on-device, surely that can, too?
I think Rust has another good alternative to this, although it might be cheating a little: you can just write (lo..hi).rev(). That way, the common case of going forwards is nice, and the case of going backward isn't…
You seem to have it backwards. The goal is to discourage future manifesto-publishers from murdering. Just as school shootings used to be a good way to get your face on TV, murder is a good way to market your manifesto.…
This manifesto is just the expression of one man's fringe political views. There is a lot of rubbish in it. For example, he spends pages insinuating that leftism is rooted in masochistic, self-hating, chauvinistic…
If you'd used 50.. instead of _, Rust would've caught this error for you. ;) https://play.rust-lang.org/?version=nightly&mode=release&edi...
Nitpick: I'm pretty sure that "11..50" should be a "10..50".
Does it still elide the bounds check if you replace the first three lines with assert_eq!(xs.len(), ys.len()); ?
What would a browser even need a backend for? The only valid use that I can think of is Google's Safe Browsing list, but if ad blocking can be implemented totally on-device, surely that can, too?
I think Rust has another good alternative to this, although it might be cheating a little: you can just write (lo..hi).rev(). That way, the common case of going forwards is nice, and the case of going backward isn't…