Comment 1:

Please attach a standalone test case to this bug report, rather than referring to the
somewhat confusing mailing list thread.  Thanks.

Comment 2 by vincent@callanan.ie:

Just tested on 1.2rc4 (Windows/AMD64).
Bug is not present.

Comment 3 by vincent@callanan.ie:

Ok, while bug is not present in 1.2rc4,
You may still need to patch 1.1.2
So here is relevant part of thread:
---------------------------------------------
This version works....
package pkgA
type item struct {
    val int
}
type ReadOnlyItem struct {
    *item
}
func (this *item) Val() int {
    return this.val
}
func GetItem() ReadOnlyItem {
    return ReadOnlyItem{&item{1234}}
}
-----------------------------------------------
package main
import (
    "....../pkgA"
    "fmt"
)
func main() {
    fmt.Println(pkgA.GetItem().Val())
}
------------------------------------------
But when I replace func GetItem() in pkgA with
func GetItem() struct{ *item } {
    return struct{ *item }{&item{1234}}
}
pkgA compiles ok, but I get the following compile error in package main at the import
"pkgA" line:
unknown struct {} field 'pkgA.item' in struct literal

Comment 4:

This is issue #5910

Comment 5 by vincent@callanan.ie:

Thanks,
I saw that bug but thought it had something to do with channels.
Out of curiosity, there appears to be some trepidation about this whole area
i.e. anonymous structs/embedded fields/inlining.
Can we assume that the relevant code is "reasonably clean" at this point (1.2rc4)?

Comment 6:

As far as we know the tools work correctly.  Of course bugs are always possible.  I
don't see any trepidation myself.

Status changed to Duplicate.

Merged into issue #5910.