lalrpop-lambda

> this is exactly why languages that specify their source code in non-ascii encodings are a bad idea. Seems like your problem isn't that the source has a specified encoding, but that the syntax allows for non-ascii characters in identifiers, which is actually an unstable feature of Rust, only available with nightly compiler builds. See the feature flag: https://github.com/nixpulvis/lalrpop-lambda/blob/master/src/... Specifying ASCII for the source code, as your post suggests is better, would leave everyone stuck using \uxxxx escapes for non-ASCII data in string literals. That's unnecessary when you instead specify UTF-8.

Sure but this is a macro that’s user defined and not in the rust source code. Here’s the macro def: https://github.com/nixpulvis/lalrpop-lambda/blob/master/src/... I think it’s important to allow Unicode for developers to be more inclusive of other languages and cultures. This is at the forefront of the community of Rust. As for keywords, yes, I’m with you there.

FWIW, I've moved this macro into https://github.com/nixpulvis/lalrpop-lambda, and it's got the start of a normalize function.