From 7841cb14d95cf64c29b865c8a761a9e00fbbb37c Mon Sep 17 00:00:00 2001
From: Josh Bleecher Snyder
- These enhancements were added to simplify writing code that conforms
+ The package unsafe enhancements were added to simplify writing code that conforms
to
The unsafe.Pointer
's safety
rules, but the rules remain unchanged. In particular, existing
programs that correctly use unsafe.Pointer
remain
@@ -735,7 +735,7 @@ func Foo() bool {
These components were always interpreted as decimal, but some operating systems treat them as octal.
This mismatch could hypothetically lead to security issues if a Go application was used to validate IP addresses
which were then used in their original form with non-Go applications which interpreted components as octal. Generally,
- it is advisable to always re-encoded values after validation, which avoids this class of parser misalignment issues.
+ it is advisable to always re-encode values after validation, which avoids this class of parser misalignment issues.
File.WriteString
method
- has been optimized to no longer make a copy of the input string.
+ has been optimized to not make a copy of the input string.
ArrayOf
function now panics when
called with a negative length.
+ Checking the Type.ConvertibleTo
method
+ is no longer sufficient to guarantee that a call to
+ Value.Convert
will not panic.
+ It may panic when converting `[]T` to `*[N]T` if the slice's length is less than N.
+ See the language changes section above.
+
The strconv
package now uses Ulf Adams's Ryū algorithm for formatting floating-point numbers.
- This algorithm improves performance on most inputs, and is more than 99% faster on worst-case inputs.
+ This algorithm improves performance on most inputs and is more than 99% faster on worst-case inputs.
-- 2.50.0