Apply suggestions from code review
Co-authored-by: memoryruins <memoryruinsmusic@gmail.com>
This commit is contained in:
parent
9348118c30
commit
9f1ad43e69
1 changed files with 2 additions and 2 deletions
|
@ -4,7 +4,7 @@ Version 1.53.0 (2021-06-17)
|
||||||
Language
|
Language
|
||||||
-----------------------
|
-----------------------
|
||||||
- [You can now use unicode for identifiers.][83799] This allows multilingual
|
- [You can now use unicode for identifiers.][83799] This allows multilingual
|
||||||
identifiers but still doesn't allow glyphs that not considered characters
|
identifiers but still doesn't allow glyphs that are not considered characters
|
||||||
such as `◆` or `🦀`. More specifically you can now use any identifier that
|
such as `◆` or `🦀`. More specifically you can now use any identifier that
|
||||||
matches the UAX #31 "Unicode Identifier and Pattern Syntax" standard. This
|
matches the UAX #31 "Unicode Identifier and Pattern Syntax" standard. This
|
||||||
is the same standard as languages like Python, however Rust uses NFC
|
is the same standard as languages like Python, however Rust uses NFC
|
||||||
|
@ -110,7 +110,7 @@ Compatibility Notes
|
||||||
-------------------
|
-------------------
|
||||||
- [Implement token-based handling of attributes during expansion][82608]
|
- [Implement token-based handling of attributes during expansion][82608]
|
||||||
- [`Ipv4::from_str` will now reject octal format IP addresses.][83652] The octal format
|
- [`Ipv4::from_str` will now reject octal format IP addresses.][83652] The octal format
|
||||||
can lead confusion and potential security vulnerablities and [is no longer recommended][ietf6943].
|
can lead to confusion and potential security vulnerabilities and [is no longer recommended][ietf6943].
|
||||||
|
|
||||||
|
|
||||||
Internal Only
|
Internal Only
|
||||||
|
|
Loading…
Add table
Reference in a new issue