From: Russ Cox Date: Wed, 6 Dec 2017 05:01:26 +0000 (-0500) Subject: doc/go1.10: fix many TODOs X-Git-Tag: go1.10beta1~17 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=c56fda63a4950a7f7eb2bda02d68b16d0d16387a;p=gostls13.git doc/go1.10: fix many TODOs Change-Id: I97a28379b1a9ca3daa875edbcd5213673ca138d0 Reviewed-on: https://go-review.googlesource.com/82115 Reviewed-by: Russ Cox --- diff --git a/doc/go1.10.html b/doc/go1.10.html index dcf45cd188..5c9e706940 100644 --- a/doc/go1.10.html +++ b/doc/go1.10.html @@ -22,16 +22,6 @@ ul li { margin: 0.5em 0; } release notes. Go 1.10 is expected to be released in February 2018.

- -

The latest Go release, version 1.10, arrives six months after go1.9. Most of its changes are in the implementation of the toolchain, runtime, and libraries. @@ -127,7 +117,7 @@ applies the flags only to the packages matching the pattern. For example: go install -ldflags=cmd/gofmt=-X=main.version=1.2.3 cmd/... installs all the commands matching cmd/... but only applies the -X option to the linker flags for cmd/gofmt. -For more details, see go help build. +For more details, see go help build.

@@ -161,7 +151,7 @@ One new requirement implied by these changes is that binary-only packages must now declare accurate import blocks in their stub source code, so that those imports can be made available when linking a program using the binary-only package. -For more details, see go help filetype. +For more details, see go help filetype.

Test

@@ -403,11 +393,6 @@ line number information is more accurate, making source-level stepping through a and each package is now presented as its own DWARF compilation unit.

-

-TODO: What to say about FMA, if anything? -The spec change was mentioned in Go 1.9 but I am not sure whether any new architectures turned it on in Go 1.10. -

-

The various build modes has been ported to more systems. @@ -557,6 +542,10 @@ There is no longer a limit on the GOMAX (In Go 1.9 the limit was 1024.)

+

+TODO: Anything about CL 59970: "runtime: separate soft and hard heap limits"? +

+

Performance

@@ -894,6 +883,16 @@ adds a new method that causes it to report inputs with unknown JSON fields as a decoding error. (The default behavior has always been to discard unknown fields.)

+ +

+As a result of fixing a reflect bug, +Unmarshal +can no longer decode into fields inside +embedded pointers to unexported struct types, +because it cannot initialize the unexported embedded pointer +to point at fresh storage. +Unmarshal now returns an error in this case. +

encoding/pem
@@ -905,10 +904,6 @@ and no longer generate partial output when presented with a block that is impossible to encode as PEM data.

- -

-TODO: Reflect fallout. -

encoding/xml
@@ -1268,7 +1263,23 @@ from a string into a byte array or byte slice, to match the

-TODO: New reflect CanSet change for pointers to unexported fields. +In structs, embedded pointers to unexported struct types were +previously incorrectly reported with an empty PkgPath +in the corresponding StructField, +with the result that for those fields, +and Value.CanSet +incorrectly returned true and +and Value.Set +incorrectly succeeded. +The underlying metadata has been corrected; +for those fields, +CanSet now correctly returns false +and Set now correctly panics. +This may affect reflection-based unmarshalers +that could previously unmarshal into such fields +but no longer can. +For example, see the encoding/json notes. +