From 014137c839a3b9c5b9a2f44df8c8598e2569a311 Mon Sep 17 00:00:00 2001
From: Russ Cox <rsc@golang.org>
Date: Mon, 10 Dec 2012 18:08:07 -0500
Subject: [PATCH] doc/go1.1.html: add warning about net.ResolveTCPAddr error
 checking

Suggested by Paul Borman.

R=golang-dev, mikioh.mikioh
CC=golang-dev
https://golang.org/cl/6930043
---
 doc/go1.1.html | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/doc/go1.1.html b/doc/go1.1.html
index c70be57fad..3e07926f29 100644
--- a/doc/go1.1.html
+++ b/doc/go1.1.html
@@ -72,6 +72,19 @@ calls the debug/elf functions Symbols or ImportedSymbols may need to be
 adjusted to account for the additional symbol and the change in symbol offsets.
 </p>
 
+<h3 id="net">net</h3>
+
+<p>
+The protocol-specific resolvers were formerly
+lax about the network name passed in. For example, although the documentation was clear
+that the only valid networks for <code>ResolveTCPAddr</code> are <code>"tcp"</code>,
+<code>"tcp4"</code>, and <code>"tcp6"</code>, 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 <code>ResolveIPAddr</code>, <code>ResolveUDPAddr</code>, and
+<code>ResolveUnixAddr</code>.
+</p>
+
+
 <h3 id="time">time</h3>
 <p>
 On Linux, previous versions of the time package returned times with
-- 
2.48.1