You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The highest valid code point is 1114111 (0x10FFFF) and the modern UTF-8
standard guarantees that the maximum number of bytes needed to encode a
code point is 4 (instead of 6, in the legacy standard).
Nominating this for the backwards compatible milestone. A simple attempted fix breaks a test in the json module so we have at least a bit of code depending on this incorrect behaviour.
Ignore str::len() in or_fun_call lint.
changelog: Changed `or_fun_call` to ignore `str::len`, in the same way it ignores `slice::len` and `array::len`
Closesrust-lang#6943
The highest valid code point is 1114111 (0x10FFFF) and the modern UTF-8
standard guarantees that the maximum number of bytes needed to encode a
code point is 4 (instead of 6, in the legacy standard).
From https://tools.ietf.org/html/rfc3629:
Changes from RFC 2279
o Restricted the range of characters to 0000-10FFFF (the UTF-16
accessible range).
The text was updated successfully, but these errors were encountered: