Commit 866f63e8 authored by Robert Griesemer's avatar Robert Griesemer

spec: refer to "not defined type" rather than "unnamed type" in conversions

We missed this in https://golang.org/cl/36213.
Thanks to Chris Hines for pointing it out.

For #18130.

Change-Id: I6279ab19966c4391c4b4458b21fd2527d3f949dd
Reviewed-on: https://go-review.googlesource.com/36691Reviewed-by: default avatarIan Lance Taylor <iant@golang.org>
parent 3fd3171c
<!--{ <!--{
"Title": "The Go Programming Language Specification", "Title": "The Go Programming Language Specification",
"Subtitle": "Version of February 7, 2017", "Subtitle": "Version of February 9, 2017",
"Path": "/ref/spec" "Path": "/ref/spec"
}--> }-->
...@@ -3908,7 +3908,8 @@ in any of these cases: ...@@ -3908,7 +3908,8 @@ in any of these cases:
</li> </li>
<li> <li>
ignoring struct tags (see below), ignoring struct tags (see below),
<code>x</code>'s type and <code>T</code> are unnamed pointer types <code>x</code>'s type and <code>T</code> are pointer types
that are not <a href="#Type_definitions">defined types</a>,
and their pointer base types have identical underlying types. and their pointer base types have identical underlying types.
</li> </li>
<li> <li>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment