diff --git a/doc/go1.2.html b/doc/go1.2.html index ec1c0259f9..e8a2b86a97 100644 --- a/doc/go1.2.html +++ b/doc/go1.2.html @@ -6,13 +6,6 @@
- -RED TEXT IS FROM THE 1.1 DOC AND NEEDS TO BE UPDATED. (It is here for -formatting and style reference.) - -
-Since the release of Go version 1.1 in April, 2013, the release schedule has been shortened to make the release process more efficient. @@ -293,58 +286,35 @@ of the tests run by the package, not just those of the package itself. By default, as before, dependencies of the tests are not downloaded.
- -
-
-The Go 1.1 tool chain adds experimental support for freebsd/arm
,
-netbsd/386
, netbsd/amd64
, netbsd/arm
,
-openbsd/386
and openbsd/amd64
platforms.
-
-
-
-An ARMv6 or later processor is required for freebsd/arm
or
-netbsd/arm
.
-
-
-
-Go 1.1 adds experimental support for cgo
on linux/arm
.
-
-
- -The performance of code compiled with the Go 1.1 gc tool suite should be noticeably -better for most Go programs. -Typical improvements relative to Go 1.0 seem to be about 30%-40%, sometimes -much more, but occasionally less or even non-existent. -There are too many small performance-driven tweaks through the tools and libraries -to list them all here, but the following major changes are worth noting: - +There are a number of significant performance improvements in the standard library; here are a few of them.
-compress/bzip2
+decompresses about 30% faster.
crypto/des
package
+is about five times faster.
encoding/json
package
+encodes about 30% faster.
-Breaking change: TODO
-archive/tar,archive/zip: fix os.FileInfo implementation to provide base name only (CL 13118043).
+The
+archive/tar
+and
+archive/zip
+packages have had a change to their semantics that may break existing programs.
+The issue is that they both provided an implementation of the
+os.FileInfo
+interface that was not compliant with the specification for that interface.
+In particular, their Name
method returned the full
+path name of the entry, but the interface specification requires that
+the method return only the base name (final path element).
+
+Updating: Since this behavior was newly implemented and +a bit obscure, it is possible that no code depends on the broken behavior. +If there are programs that do depend on it, they will need to be identified +and fixed manually.
-encoding: TODO new package defining generic encoding interfaces (CL 12541051).
+There is a new package, encoding
,
+that defines a set of standard encoding interfaces that may be used to
+build custom marshalers and unmarshalers for packages such as
+encoding/xml
,
+encoding/json
,
+and
+encoding/binary
.
+These new interfaces have been used to tidy up some implementations in
+the standard library.
+
+The new interfaces are called
+BinaryMarshaler
,
+BinaryUnmarshaler
,
+TextMarshaler
,
+and
+TextUnmarshaler
.
+Full details are in the documentation for the package
+and a separate design document.
the result is ""c a b"
. The [3]
index accesses the third formatting
-argument, whch is 'c'
, [1]
accesses the first, 'a'
,
+argument, which is 'c'
, [1]
accesses the first, 'a'
,
and then the next fetch accesses the argument following that one, 'b'
.
encoding/gob
package
-now supports the generic encoding interfaces of the
+now treats channel and function fields of structures as if they were unexported,
+even if they are not. That is, it ignores them completely. Previously they would
+trigger an error, which could cause unexpected compatibility problems if an
+embedded structure added such a field.
+The package also now supports the generic encoding interfaces of the
encoding
package
described above.
MarshalerAttr
and
UnmarshalerAttr
interfaces.
+The package also adds a
+Flush
method
+to the
+Encoder
+type for use by custom encoders. See the documentation for
+EncodeToken
+to see how to use it.
net/http
package will no longer
+transmit cookies that are incorrect according to
+RFC 6265.
+It just logs an error and sends nothing.
+Also,
+the net/http
package's
+ReadResponse
+function now permits the *Request
parameter to be nil
,
+whereupon it assumes a GET request.
+Finally, an HTTP server will now serve HEAD
+requests transparently, without the need for special casing in handler code.
+While serving a HEAD request, writes to a
+Handler
's
+ResponseWriter
+are absorbed by the
+Server
+and the client receives an empty body as required by the HTTP specification.
testing
package
-now exports theTB
interface.
+now exports the TB
interface.
It records the methods in common with the
T
and