<p dir="auto">by <strong>runningwild</strong>:</p>
<pre class="notranslate">If there are no blank lines between the start of a file and a comment containing build
constraints those build constraints are ignored.

What steps will reproduce the problem?
Make two files, foo.go (no blank line before the build constraint):
// +build ignore
package main
func main() {
  println("Hi!")
}
and bar.go:
package main
func main() {
  println("Hi!")
}

then run "go build ." in that directory.

This fails because of duplicate definition of main().  If a blank line is inserted
before the build constraint in foo.go the compilation succeeds as expected (inserting
another line of comments is not sufficient).

Which compiler are you using (5g, 6g, 8g, gccgo)?
6g

Which operating system are you using?
darwin, linux

Which version are you using?  (run 'go version')
go1
hg id: 817fde92780a</pre>
<pre class="notranslate"><a href="http://play.golang.org/p/T9zdkbOhqw" rel="nofollow">http://play.golang.org/p/T9zdkbOhqw</a>

In this (perverse) program, x is a pointer to a struct, and (*x).y is a legal
expression, but x.y() is not.  This contradicts the letter of the spec, though I think
not its spirit. 

type T struct{}
func (T) y() {}

type X *T

var x X

// "Selectors automatically dereference pointers to structs.
// If x is a pointer to a struct, x.y is shorthand for (*x).y."
(*x).y()
x.y() // gc error: x.y undefined (type X has no field or method y)</pre>