From: Ian Lance Taylor Date: Wed, 18 Jul 2018 20:19:04 +0000 (-0700) Subject: doc: update go1.11 release notes X-Git-Tag: go1.11beta2~42 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=ee198df4cdc2e49c7376f99d9d3081da6ebae836;p=gostls13.git doc: update go1.11 release notes Change-Id: I806d411c075cdc66322112b6ee5e50f58462bc6b Reviewed-on: https://go-review.googlesource.com/124776 Reviewed-by: Ian Lance Taylor --- diff --git a/doc/go1.11.html b/doc/go1.11.html index a070442535..87c687cb64 100644 --- a/doc/go1.11.html +++ b/doc/go1.11.html @@ -453,7 +453,8 @@ for k := range m {
debug/elf

- TODO: https://golang.org/cl/112115: add machine and OSABI constants + More ELFOSABI and EM constants have + been added.

@@ -469,7 +470,10 @@ for k := range m {
encoding/base32

- TODO: https://golang.org/cl/112516: handle surplus padding consistently + The decoder now consistently + returns io.ErrUnexpectedEOF for an incomplete + chunk. Previously it would return io.EOF in some + cases.

@@ -477,7 +481,9 @@ for k := range m {
encoding/csv

- TODO: https://golang.org/cl/99696: disallow quote for use as Comma + The Reader now rejects attempts to set + the Comma field to a double-quote character, as + double-quote characters already have a special meaning in CSV.

@@ -485,7 +491,11 @@ for k := range m {
go/scanner

- TODO: https://golang.org/cl/100235: report errors for incorrect line directives + The package no longer modifies filenames in //line + directives when recording position information or reporting + errors. Previously the package would change relative paths + in //line directives to absolute paths by + prepending the source file directory.

@@ -493,7 +503,12 @@ for k := range m {
html/template

- TODO: https://golang.org/cl/121815: ignore untyped nil arguments to default escapers + The package has changed its behavior when a typed interface + value is passed to an implicit escaper function. Previously such + a value was written out as (an escaped form) + of <nil>. Now such values are ignored, just + as an untyped nil value is (and always has been) + ignored.

@@ -769,10 +784,9 @@ for k := range m {

- In previous versions, passing an untyped nil to a template function - would result in an incorrect error stating that the function was missing an argument. - Errors resulting from untyped nil values being passed to template-evaluated functions - are now properly reported. + In previous versions untyped nil values passed to + template functions were ignored. They are now passed as normal + arguments.