1# RUN: yaml-bench -canonical %s 2>&1 | FileCheck %s --strict-whitespace 2# CHECK: "as space trimmed\nspecific\L escaped\t none" 3 4## Note: The example was originally taken from Spec 1.1, but the parsing rules 5## have been changed since then. 6## * The line-separator character '\u2028' is no longer considered a line-break 7## character, so the line "...specific\u2028\nescaped..." is now parsed as 8## "...specific\L escaped...". 9## * The paragraph-separator character '\u2029' is also excluded from line-break 10## characters, so the original sequence "escaped\t\\\u2029" is no longer 11## considered valid. This is replaced by "escaped\t\\\n" in the test source, 12# so the output has changed as well. 13## See https://yaml.org/spec/1.2.2/ext/changes/ for details. 14## 15## Note 2: Different parsers handle this corner case example differently. 16## * https://github.com/yaml/libyaml: 17## "as space trimmed\nspecific\L\nescaped\t\nnone" 18## * https://github.com/yaml/yaml-reference-parser (parser-1.2): 19## "as space trimmed\nspecific\L escaped\t none" 20## * https://github.com/yaml/yaml-reference-parser (parser-1.3): 21## "as space trimmed\nspecific escaped\t none" 22 23 "as space 24 trimmed 25 26 specific 27 escaped \ 28 29 none" 30