1
0
mirror of https://github.com/golang/go synced 2024-11-24 19:40:09 -07:00
go/test/interface
Russ Cox 196b663075 gc: implement == on structs and arrays
To allow these types as map keys, we must fill in
equal and hash functions in their algorithm tables.
Structs or arrays that are "just memory", like [2]int,
can and do continue to use the AMEM algorithm.
Structs or arrays that contain special values like
strings or interface values use generated functions
for both equal and hash.

The runtime helper func runtime.equal(t, x, y) bool handles
the general equality case for x == y and calls out to
the equal implementation in the algorithm table.

For short values (<= 4 struct fields or array elements),
the sequence of elementwise comparisons is inlined
instead of calling runtime.equal.

R=ken, mpimenov
CC=golang-dev
https://golang.org/cl/5451105
2011-12-12 22:22:09 -05:00
..
bigdata.go
convert1.go
convert2.go
convert.go
embed0.go
embed1.go
embed2.go
embed.go
explicit.go
fail.go test: silence/coalesce some tests 2011-09-26 19:35:21 -04:00
fake.go reflect: disallow Interface method on Value obtained via unexported name 2011-10-17 18:48:45 -04:00
noeq.go gc: implement == on structs and arrays 2011-12-12 22:22:09 -05:00
pointer.go test: match gccgo error messages 2011-09-21 17:25:48 -07:00
private1.go
private.go
receiver1.go
receiver.go
recursive.go
returntype.go test: silence/coalesce some tests 2011-09-26 19:35:21 -04:00
struct.go