From ee198df4cdc2e49c7376f99d9d3081da6ebae836 Mon Sep 17 00:00:00 2001
From: Ian Lance Taylor
- TODO: https://golang.org/cl/112115: add machine and OSABI constants
+ More
- TODO: https://golang.org/cl/112516: handle surplus padding consistently
+ The decoder now consistently
+ returns
- TODO: https://golang.org/cl/99696: disallow quote for use as Comma
+ The
- TODO: https://golang.org/cl/100235: report errors for incorrect line directives
+ The package no longer modifies filenames in
- 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
@@ -469,7 +470,10 @@ for k := range m {
ELFOSABI
and EM
constants have
+ been added.
@@ -477,7 +481,9 @@ for k := range m {
io.ErrUnexpectedEOF
for an incomplete
+ chunk. Previously it would return io.EOF
in some
+ cases.
@@ -485,7 +491,11 @@ for k := range m {
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.
@@ -493,7 +503,12 @@ for k := range m {
//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.
@@ -769,10 +784,9 @@ for k := range m {
<nil>
. Now such values are ignored, just
+ as an untyped nil
value is (and always has been)
+ ignored.
- 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.