Pre- and post-increment are only really useful when you're doing C-style looping and there's a good reason we don't do that in Rust.
I actually honestly can't recall ever making an off by one error in Rust, I'm sure when implementing specific data structures or when doing pointer manipulation it's still a possibility but you can write a gazillion lines of code without ever running risk of that particular annoyance. Also while C folks may have an argument regarding operator semantics, C++ folks don't they're doing unspeakable things to <<.
Also, FWIW Haskell uses ++ to append lists and therefore also strings. It's not like it's an odd-ball usage of the symbols, that'd be .. which I vaguely remember some language using. Would cause a whole new class of confusion regarding 'a'..'z' vs. "a".."z". Not to mention that "aa".."zz" actually makes sense as a range all that's missing is &str: Step. Probably not a good idea to have built-in because do we mean printable ASCII? Whole unicode range? Just the alphabet? Not an issue when you're doing it to single chars but strings get ambiguous fast. Does Rust even guarantee stuff about Char ordering C certainly doesn't really do that, short of I think 0..9 being contiguous.
Unlikely, and even more unlikely to not be able to be worked around by a local rust user group.
Like, the .eu restriction to only give out domains to individuals and companies within the EEA is more about having a domestic contact than anything else, EURid doesn't care who actually uses the domain just that it has European legal representation.