I have to agree with @kunerd — I think that Rust is already quite complex, we should not add unnecessary complication to it, it would just result in compiler bugs in exchange for a tiny, short-lived convenience for a minute fraction of people. The language being smaller, more uniform, more consistent, and not containing Every Currently Fashionable Minor Feature Ever™ is one primary reason people choose Rust over C++, for example.
The few dozen English keywords are not hard to learn, and quite frankly I would be very upset if I had to read code with non-English keywords. Consider what happens, for example, when you are trying to read the code outside of your IDE, in plaintext, or online in a Git repository. For example, you are on your way, when someone asks you to review some code. Or you need to temporarily work on a machine with only a basic text editor. Now your IDE isn’t at hand to translate the “Rust” code from their native language — which you have no idea how to read! This means that you can’t read and review the code, maybe you’ll waste the other party’s time since they will have to wait, or they’ll commit in the code unreviewed, leading to bugs…
My ultimate point is: we should try to unify communication, that’s how people all over the world can co-operate on projects. And that is done by agreeing on a common language, not by splitting code up into several sub-languages or dialects.
For example, in Haskell, where everyone invents their own clever operators and basically every individual writes in a different domain-specific language, it’s a pain to read others’ code, it’s a disaster. The concept of “translating” a programming language was always puzzling to me, it simply doesn’t seem to make much sense. There’s no real benefit to it, and it would just complicate matters.
As you can probably tell by now, I’m not a native English speaker, but I firmly believe that even with a basic level of English knowledge, it’s perfectly possible to get started with an English-based programming language. I was 9 when I was getting started with coding in BASIC, and it was the very same year that I first learned English in school. So I wasn’t a fluent user at the time — yet I found English keywords the least hard part of learning to program. And if one is a seasoned programmer, the principle applies to them to an even higher degree.
To add to this, I can tell two related personal stories. The first one is: I once had to work on a Linux-based system that somehow ended up with a GCC installation localized to French. The damn compiler was spitting out error messages in French and I have no idea what they meant, it was extremely frustrating.
The other story is: the university I went to (and am currently teaching at) has a strange, in-house educational programming language that uses keywords and type names in Hungarian, which is our native language. This is supposedly done so that “students find it easier to get started”. But students hate it passionately. They always complain about it, and there’s nothing I can do because it’s faculty policy to use that language in the first semester of Intro to Programming.