> 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 speci

> 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/lib.rs#L1 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.