rust/tests/ui/parser/parser-unicode-whitespace.rs

// run-pass
// Beware editing: it has numerous whitespace characters which are important.
// It contains one ranges from the 'PATTERN_WHITE_SPACE' property outlined in
// https://unicode.org/Public/UNIDATA/PropList.txt
//
// The characters in the first expression of the assertion can be generated
// from: "4\u{0C}+\n\t\r7\t*\u{20}2\u{85}/\u{200E}3\u{200F}*\u{2028}2\u{2029}"
pub fn main() {
assert_eq!(4+

7   * 2/‎3‏* 2 , 4 + 7 * 2 / 3 * 2);
}
-												tests: Add missing run-pass annotations

											
										
										
											2019-07-26 21:54:25 +00:00
+								// run-pass
-												libsyntax: accept only whitespace with the PATTERN_WHITE_SPACE property

This aligns with unicode recommendations and should be stable for all future
unicode releases. See http://unicode.org/reports/tr31/#R3.

This renames `libsyntax::lexer::is_whitespace` to `is_pattern_whitespace`
so potentially breaks users of libsyntax.

											
										
										
											2015-11-12 02:43:43 +00:00
+								// Beware editing: it has numerous whitespace characters which are important.
 								// It contains one ranges from the 'PATTERN_WHITE_SPACE' property outlined in
-												Use HTTPS links where possible

											
										
										
											2021-06-23 20:26:46 +00:00
+								// https://unicode.org/Public/UNIDATA/PropList.txt
-												libsyntax: accept only whitespace with the PATTERN_WHITE_SPACE property

This aligns with unicode recommendations and should be stable for all future
unicode releases. See http://unicode.org/reports/tr31/#R3.

This renames `libsyntax::lexer::is_whitespace` to `is_pattern_whitespace`
so potentially breaks users of libsyntax.

											
										
										
											2015-11-12 02:43:43 +00:00
+								//
 								// The characters in the first expression of the assertion can be generated
 								// from: "4\u{0C}+\n\t\r7\t*\u{20}2\u{85}/\u{200E}3\u{200F}*\u{2028}2\u{2029}"
-												libsyntax: use char::is_whitespace instead of custom implementations

Fixes #29590.

											
										
										
											2015-11-09 21:04:31 +00:00
+								pub fn main() {
-												libsyntax: accept only whitespace with the PATTERN_WHITE_SPACE property

This aligns with unicode recommendations and should be stable for all future
unicode releases. See http://unicode.org/reports/tr31/#R3.

This renames `libsyntax::lexer::is_whitespace` to `is_pattern_whitespace`
so potentially breaks users of libsyntax.

											
										
										
											2015-11-12 02:43:43 +00:00
+								assert_eq!(4+
-												libsyntax: use char::is_whitespace instead of custom implementations

Fixes #29590.

											
										
										
											2015-11-09 21:04:31 +00:00
-												libsyntax: accept only whitespace with the PATTERN_WHITE_SPACE property

This aligns with unicode recommendations and should be stable for all future
unicode releases. See http://unicode.org/reports/tr31/#R3.

This renames `libsyntax::lexer::is_whitespace` to `is_pattern_whitespace`
so potentially breaks users of libsyntax.

											
										
										
											2015-11-12 02:43:43 +00:00
+* 2/‎3‏* 2 , 4 + 7 * 2 / 3 * 2);
-												libsyntax: use char::is_whitespace instead of custom implementations

Fixes #29590.

											
										
										
											2015-11-09 21:04:31 +00:00
+								}