rust/tests/ui/lint/rfc-2457-non-ascii-idents/lint-uncommon-codepoints.rs

#![deny(uncommon_codepoints)]

const µ: f64 = 0.000001; //~ ERROR identifier contains uncommon Unicode codepoints
//~| WARNING should have an upper case name

fn dĳkstra() {} //~ ERROR identifier contains uncommon Unicode codepoints

fn main() {
    let ㇻㇲㇳ = "rust"; //~ ERROR identifier contains uncommon Unicode codepoints

    // using the same identifier the second time won't trigger the lint.
    println!("{}", ㇻㇲㇳ);
}
Implement uncommon_codepoints lint. 2020-01-02 06:02:22 -06:00			`#![deny(uncommon_codepoints)]`

			`const µ: f64 = 0.000001; //~ ERROR identifier contains uncommon Unicode codepoints`
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors. 2021-07-20 22:23:22 -05:00			`//~\| WARNING should have an upper case name`
Implement uncommon_codepoints lint. 2020-01-02 06:02:22 -06:00
			`fn dĳkstra() {} //~ ERROR identifier contains uncommon Unicode codepoints`

			`fn main() {`
			`let ㇻㇲㇳ = "rust"; //~ ERROR identifier contains uncommon Unicode codepoints`
Refactor non_ascii_idents lints, exclude ascii pair for confusable_idents lint. 2020-05-09 20:10:15 -05:00
			`// using the same identifier the second time won't trigger the lint.`
			`println!("{}", ㇻㇲㇳ);`
Implement uncommon_codepoints lint. 2020-01-02 06:02:22 -06:00			`}`