Lines Matching +refs:generic +refs:normalize +refs:comments
61 I should make separate decisions about permitting Unicode in comments,
72 strings are legal as Symbols, and we'll NFC normalize, to eliminate
75 ## Unicode comments
76 This is relatively safe, since comments are (for now) uninterpreted.
77 If Curv gets "documentation comments", then issues may arise.
95 If I support Unicode identifiers, then I *must* normalize to NFC before
238 If I don't normalize strings on construction, and I don't normalize on
246 But this means, two strings that normalize to the same thing may be
259 * Is it easier or harder to pre-normalize all Curv strings and then
281 * Maybe we normalize strings to NFC before conversion to field names.
321 are the same thing. The only time we normalize strings is when receiving
324 normalize their output. `decode` just rejects code points it doesn't like.
468 * The generic equality operator has special rules for contiguous subsequences
470 * The generic equality operator just implements simple list equality, and
510 When you normalize a string, it mallocs a new buffer for the result,