String comparison: Difference between revisions

BewareBe aware that Raku applies normalization (Unicode NFC form (Normalization Form Canonical)) by default to all input and output except for file names<ref> [https://docs.raku.org/language/unicode</ref> See docs]. ShortlyRaku putfollows yourthe Unicode stringspec. willRaku rarelyfollows be'''all''' whatof youthe expectUnicode whenspec, youincluding includeparts charactersthat outsidesome people don't like. There are some graphemes for which the ASCIIUnicode rangeconsortium has specified that the NFC form is a different (though usually visually identical) grapheme. Referred to in [https://www.unicode.org/reports/tr15 Unicode standard annex #15] as '''Canonical Equivalence'''. Raku adheres to that spec.

say ($kelvin === $k); # True, identical objects</syntaxhighlight>

In most programming language the previous two objects wouldn't be equivalent, but insince Raku therefollows arethe sinceUnicode specification, and normalization is applied by default automatically, andthey show can'tup beas disabledequivalent.

It's officially identified as a commonpossible trap for string handling<ref>. [https://docs.raku.org/language/traps#All_text_is_normalized_by_default</ref> See docs].