4 ms·
>You're imagining something which can't exist. Excuse me, what is hard in taking this: https://doc.rust-lang.org/book/appendix-01-keywords.html https://doc.rus
by aredox 2y ago
>You're imagining something which can't exist.
Excuse me, what is hard in taking this:
https://doc.rust-lang.org/book/appendix-01-keywords.html https://doc.rust-lang.org/book/appendix-01-keywords.html
And translating those back and forth?
In fact, if it "can't exist", how can Rost be "fully compatible with English-Rust, so you can mix both at your convenience"?
And Rouille?
https://github.com/bnjbvr/rouille https://github.com/bnjbvr/rouille
And Unirust?
https://github.com/charyan/unirust https://github.com/charyan/unirust
- user_of_the_wek 2y agoI would assume that in rust, as in other languages, you can't use keywords as e.g. variable names because it would lead to mixups. So you can't translate programs back and forth without making sure you don't use keyword of _any_ possible language as variable names.
- tialaramex 2y agoFor keywords in particular you can write the identifier anyway, r#async is a perfectly reasonable (though ugly) way to use async as an identifier, despite the fact that async is a keyword in current Rust editions. But the problem is that while we can mechanically perform the operation that doesn't have the effect claimed, it's as if people expected (and I know this does happen with idiots) that Chinese is just the same as English but with different symbols.