From: Robert Griesemer Date: Fri, 22 Mar 2013 23:41:27 +0000 (-0700) Subject: doc/go1.1.html: fix broken links X-Git-Tag: go1.1rc2~367 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=259e8cec7ad3d7c0031c53d70442fafdbdabe528;p=gostls13.git doc/go1.1.html: fix broken links R=golang-dev, r CC=golang-dev https://golang.org/cl/7834049 --- diff --git a/doc/go1.1.html b/doc/go1.1.html index 050a129fab..f1d490f412 100644 --- a/doc/go1.1.html +++ b/doc/go1.1.html @@ -384,9 +384,9 @@ that the only valid networks for are "tcp", "tcp4", and "tcp6", the Go 1.0 implementation silently accepted any string. The Go 1.1 implementation returns an error if the network is not one of those strings. -The same is true of the other protocol-specific resolvers ResolveIPAddr, -ResolveUDPAddr, and -ResolveUnixAddr. +The same is true of the other protocol-specific resolvers ResolveIPAddr, +ResolveUDPAddr, and +ResolveUnixAddr.

@@ -396,7 +396,7 @@ returned a UDPConn as a representation of the connection endpoint. The Go 1.1 implementation instead returns a -UnixConn +UnixConn to allow reading and writing with its ReadFrom @@ -683,11 +683,11 @@ to define the boundary separator used to package the output.

  • The net package's -net/ListenUnixgram +net/ListenUnixgram function has changed return types: it now returns a -net/UnixConn +net/UnixConn rather than a -net/UDPConn, which was +net/UDPConn, which was clearly a mistake in Go 1.0. Since this API change fixes a bug, it is permitted by the Go 1 compatibility rules.