github
/
tinygo
mirror of https://github.com/tinygo-org/tinygo.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
3903 Commits
99 Branches
41 Tags
26 MiB
Tree: 2e76cd3687
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '2e76cd3687'
${ noResults }
tinygo/testdata/reflect.txt

451 lines
10 KiB
Raw Normal View History

reflect: add reflect.TypeOf This is the beginning of true reflection support in TinyGo.
6 years ago
matching types
true
false
false
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
false
false
false
reflect: add support for non-named basic types
6 years ago
values of interfaces
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: bool name=bool
reflect: add support for non-named basic types
6 years ago
bool: true
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: bool name=bool
reflect: add support for non-named basic types
6 years ago
bool: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int name=int
reflect: add support for non-named basic types
6 years ago
int: 2000
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int name=int
reflect: add support for non-named basic types
6 years ago
int: -2000
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint name=uint
reflect: add support for non-named basic types
6 years ago
uint: 2000
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int8 name=int8
reflect: add support for non-named basic types
6 years ago
int: -3
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int8 name=int8
reflect: add support for non-named basic types
6 years ago
int: 3
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 name=uint8
reflect: add support for non-named basic types
6 years ago
uint: 200
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int16 name=int16
reflect: add support for non-named basic types
6 years ago
int: -300
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int16 name=int16
reflect: add support for non-named basic types
6 years ago
int: 300
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint16 name=uint16
reflect: add support for non-named basic types
6 years ago
uint: 50000
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int32 name=int32
reflect: add support for non-named basic types
6 years ago
int: 7340032
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int32 name=int32
reflect: add support for non-named basic types
6 years ago
int: -7340032
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint32 name=uint32
reflect: add support for non-named basic types
6 years ago
uint: 7340032
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int64 name=int64
reflect: add support for non-named basic types
6 years ago
int: 9895604649984
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int64 name=int64
reflect: add support for non-named basic types
6 years ago
int: -9895604649984
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint64 name=uint64
reflect: add support for non-named basic types
6 years ago
uint: 9895604649984
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uintptr name=uintptr
reflect: add support for non-named basic types
6 years ago
uint: 12345
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: float32 name=float32
reflect: add support for non-named basic types
6 years ago
float: +3.140000e+000
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: float64 name=float64
reflect: add support for non-named basic types
6 years ago
float: +3.140000e+000
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: complex64 name=complex64
reflect: add support for non-named basic types
6 years ago
complex: (+1.200000e+000+3.000000e-001i)
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: complex128 name=complex128
reflect: add support for non-named basic types
6 years ago
complex: (+1.300000e+000+4.000000e-001i)
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int name=myint
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
int: 32
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: string name=string
reflect: support slices and indexing of strings and slices
6 years ago
string: foo 3
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 name=uint8
reflect: support slices and indexing of strings and slices
6 years ago
uint: 102
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 name=uint8
reflect: support slices and indexing of strings and slices
6 years ago
uint: 111
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 name=uint8
reflect: support slices and indexing of strings and slices
6 years ago
uint: 111
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: unsafe.Pointer name=Pointer
reflect: add support for non-named basic types
6 years ago
pointer: true
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
reflect type: chan
chan: int
nil: true
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: chan name=mychan
reflect: add support for named types With this change, it becomes possible to get the element type of named slices, pointers, and channels. This is a prerequisite to enable the common named struct types. There's more to come.
5 years ago
chan: int
nil: true
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
reflect type: ptr
pointer: true int
nil: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int settable=true addrable=true name=int
reflect: implement Value.Set*() for basic types
6 years ago
int: 0
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
reflect type: ptr
pointer: true interface
nil: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: interface settable=true addrable=true name=error
reflect: implement Value.Set*() for basic types
6 years ago
interface
nil: true
compiler,reflect: fix NumMethods for Interface type
5 months ago
NumMethod: 1
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
reflect type: ptr
pointer: true int
nil: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int settable=true addrable=true name=int
reflect: implement Value.Set*() for basic types
6 years ago
int: 42
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: ptr name=myptr
reflect: add support for named types With this change, it becomes possible to get the element type of named slices, pointers, and channels. This is a prerequisite to enable the common named struct types. There's more to come.
5 years ago
pointer: true int
nil: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int settable=true addrable=true name=int
reflect: add support for named types With this change, it becomes possible to get the element type of named slices, pointers, and channels. This is a prerequisite to enable the common named struct types. There's more to come.
5 years ago
int: 0
reflect: implement t.Comparable() This is necessary to support the context package, which is a dependency of a lot of packages.
5 years ago
reflect type: slice comparable=false
reflect: support slices and indexing of strings and slices
6 years ago
slice: uint8 3 3
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
pointer: true
nil: false
reflect: support slices and indexing of strings and slices
6 years ago
indexing: 0
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 settable=true addrable=true name=uint8
reflect: support slices and indexing of strings and slices
6 years ago
uint: 1
indexing: 1
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 settable=true addrable=true name=uint8
reflect: support slices and indexing of strings and slices
6 years ago
uint: 2
indexing: 2
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 settable=true addrable=true name=uint8
reflect: support slices and indexing of strings and slices
6 years ago
uint: 3
reflect: implement t.Comparable() This is necessary to support the context package, which is a dependency of a lot of packages.
5 years ago
reflect type: slice comparable=false
reflect: support slices and indexing of strings and slices
6 years ago
slice: uint8 2 5
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
pointer: true
nil: false
reflect: support slices and indexing of strings and slices
6 years ago
indexing: 0
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 settable=true addrable=true name=uint8
reflect: support slices and indexing of strings and slices
6 years ago
uint: 0
indexing: 1
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 settable=true addrable=true name=uint8
reflect: support slices and indexing of strings and slices
6 years ago
uint: 0
reflect: implement t.Comparable() This is necessary to support the context package, which is a dependency of a lot of packages.
5 years ago
reflect type: slice comparable=false
reflect: support slices and indexing of strings and slices
6 years ago
slice: int32 2 2
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
pointer: true
nil: false
reflect: support slices and indexing of strings and slices
6 years ago
indexing: 0
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int32 settable=true addrable=true name=int32
reflect: support slices and indexing of strings and slices
6 years ago
int: 3
indexing: 1
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int32 settable=true addrable=true name=int32
reflect: support slices and indexing of strings and slices
6 years ago
int: 5
reflect: implement t.Comparable() This is necessary to support the context package, which is a dependency of a lot of packages.
5 years ago
reflect type: slice comparable=false
reflect: support slices and indexing of strings and slices
6 years ago
slice: string 2 2
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
pointer: true
nil: false
reflect: support slices and indexing of strings and slices
6 years ago
indexing: 0
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: string settable=true addrable=true name=string
reflect: support slices and indexing of strings and slices
6 years ago
string: xyz 3
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 name=uint8
reflect: support slices and indexing of strings and slices
6 years ago
uint: 120
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 name=uint8
reflect: support slices and indexing of strings and slices
6 years ago
uint: 121
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 name=uint8
reflect: support slices and indexing of strings and slices
6 years ago
uint: 122
indexing: 1
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: string settable=true addrable=true name=string
reflect: support slices and indexing of strings and slices
6 years ago
string: Z 1
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 name=uint8
reflect: support slices and indexing of strings and slices
6 years ago
uint: 90
reflect: implement t.Comparable() This is necessary to support the context package, which is a dependency of a lot of packages.
5 years ago
reflect type: slice comparable=false
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
slice: uint8 0 0
pointer: false
nil: true
reflect: implement t.Comparable() This is necessary to support the context package, which is a dependency of a lot of packages.
5 years ago
reflect type: slice comparable=false
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
slice: uint8 0 0
pointer: true
nil: false
reflect: implement t.Comparable() This is necessary to support the context package, which is a dependency of a lot of packages.
5 years ago
reflect type: slice comparable=false
reflect: implement Value.Set*() for basic types
6 years ago
slice: float32 2 2
pointer: true
nil: false
indexing: 0
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: float32 settable=true addrable=true name=float32
reflect: implement Value.Set*() for basic types
6 years ago
float: +1.000000e+000
indexing: 1
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: float32 settable=true addrable=true name=float32
reflect: implement Value.Set*() for basic types
6 years ago
float: +1.320000e+000
reflect: implement t.Comparable() This is necessary to support the context package, which is a dependency of a lot of packages.
5 years ago
reflect type: slice comparable=false
reflect: implement Value.Set*() for basic types
6 years ago
slice: float64 2 2
pointer: true
nil: false
indexing: 0
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: float64 settable=true addrable=true name=float64
reflect: implement Value.Set*() for basic types
6 years ago
float: +1.000000e+000
indexing: 1
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: float64 settable=true addrable=true name=float64
reflect: implement Value.Set*() for basic types
6 years ago
float: +1.640000e+000
reflect: implement t.Comparable() This is necessary to support the context package, which is a dependency of a lot of packages.
5 years ago
reflect type: slice comparable=false
reflect: implement Value.Set*() for basic types
6 years ago
slice: complex64 2 2
pointer: true
nil: false
indexing: 0
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: complex64 settable=true addrable=true name=complex64
reflect: implement Value.Set*() for basic types
6 years ago
complex: (+1.000000e+000+0.000000e+000i)
indexing: 1
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: complex64 settable=true addrable=true name=complex64
reflect: implement Value.Set*() for basic types
6 years ago
complex: (+1.640000e+000+3.000000e-001i)
reflect: implement t.Comparable() This is necessary to support the context package, which is a dependency of a lot of packages.
5 years ago
reflect type: slice comparable=false
reflect: implement Value.Set*() for basic types
6 years ago
slice: complex128 2 2
pointer: true
nil: false
indexing: 0
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: complex128 settable=true addrable=true name=complex128
reflect: implement Value.Set*() for basic types
6 years ago
complex: (+1.000000e+000+0.000000e+000i)
indexing: 1
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: complex128 settable=true addrable=true name=complex128
reflect: implement Value.Set*() for basic types
6 years ago
complex: (+1.128000e+000+4.000000e-001i)
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: slice comparable=false name=myslice
reflect: add support for named types With this change, it becomes possible to get the element type of named slices, pointers, and channels. This is a prerequisite to enable the common named struct types. There's more to come.
5 years ago
slice: uint8 3 3
pointer: true
nil: false
indexing: 0
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 settable=true addrable=true name=uint8
reflect: add support for named types With this change, it becomes possible to get the element type of named slices, pointers, and channels. This is a prerequisite to enable the common named struct types. There's more to come.
5 years ago
uint: 5
indexing: 1
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 settable=true addrable=true name=uint8
reflect: add support for named types With this change, it becomes possible to get the element type of named slices, pointers, and channels. This is a prerequisite to enable the common named struct types. There's more to come.
5 years ago
uint: 3
indexing: 2
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 settable=true addrable=true name=uint8
reflect: add support for named types With this change, it becomes possible to get the element type of named slices, pointers, and channels. This is a prerequisite to enable the common named struct types. There's more to come.
5 years ago
uint: 11
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
reflect type: array
reflect: implement support for array types
5 years ago
array: 3 int64 24
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int64 name=int64
reflect: implement support for array types
5 years ago
int: 5
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int64 name=int64
reflect: implement support for array types
5 years ago
int: 8
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int64 name=int64
reflect: implement support for array types
5 years ago
int: 2
reflect type: array
array: 2 uint8 2
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 name=uint8
reflect: implement support for array types
5 years ago
uint: 3
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 name=uint8
reflect: implement support for array types
5 years ago
uint: 5
reflect: implement t.Comparable() This is necessary to support the context package, which is a dependency of a lot of packages.
5 years ago
reflect type: func comparable=false
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
func
nil: true
reflect: implement t.Comparable() This is necessary to support the context package, which is a dependency of a lot of packages.
5 years ago
reflect type: func comparable=false
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
func
nil: false
reflect: implement t.Comparable() This is necessary to support the context package, which is a dependency of a lot of packages.
5 years ago
reflect type: map comparable=false
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
map
nil: true
reflect: implement t.Comparable() This is necessary to support the context package, which is a dependency of a lot of packages.
5 years ago
reflect type: map comparable=false
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
map
nil: false
reflect type: struct
reflect: add support for struct types
5 years ago
struct: 0
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
reflect type: struct
reflect: add support for struct types
5 years ago
struct: 1
field: 0 error
compiler,reflect: fix pkgpath for struct fields
2 years ago
pkg: main
reflect: make sure null bytes are supported in tags
2 years ago
tag: ""
reflect: add support for struct types
5 years ago
embedded: true
reflect: add StructField.IsExported method This field was introduced in Go 1.17 and is used by the encoding/json package (starting with Go 1.17).
3 years ago
exported: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: interface caninterface=false name=error
reflect: add support for struct types
5 years ago
interface
nil: true
compiler,reflect: fix NumMethods for Interface type
5 months ago
NumMethod: 1
reflect: add support for struct types
5 years ago
reflect type: struct
struct: 3
field: 0 a
compiler,reflect: fix pkgpath for struct fields
2 years ago
pkg: main
reflect: make sure null bytes are supported in tags
2 years ago
tag: ""
reflect: add support for struct types
5 years ago
embedded: false
reflect: add StructField.IsExported method This field was introduced in Go 1.17 and is used by the encoding/json package (starting with Go 1.17).
3 years ago
exported: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 caninterface=false name=uint8
reflect: add support for struct types
5 years ago
uint: 42
field: 1 b
compiler,reflect: fix pkgpath for struct fields
2 years ago
pkg: main
reflect: make sure null bytes are supported in tags
2 years ago
tag: ""
reflect: add support for struct types
5 years ago
embedded: false
reflect: add StructField.IsExported method This field was introduced in Go 1.17 and is used by the encoding/json package (starting with Go 1.17).
3 years ago
exported: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int16 caninterface=false name=int16
reflect: add support for struct types
5 years ago
int: 321
field: 2 c
compiler,reflect: fix pkgpath for struct fields
2 years ago
pkg: main
reflect: make sure null bytes are supported in tags
2 years ago
tag: ""
reflect: add support for struct types
5 years ago
embedded: false
reflect: add StructField.IsExported method This field was introduced in Go 1.17 and is used by the encoding/json package (starting with Go 1.17).
3 years ago
exported: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int8 caninterface=false name=int8
reflect: add support for struct types
5 years ago
int: 123
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: struct comparable=false name=mystruct
reflect: add support for struct types
5 years ago
struct: 5
field: 0 n
compiler,reflect: fix pkgpath for struct fields
2 years ago
pkg: main
reflect: make sure null bytes are supported in tags
2 years ago
tag: "foo:\"bar\""
reflect: add support for struct types
5 years ago
embedded: false
reflect: add StructField.IsExported method This field was introduced in Go 1.17 and is used by the encoding/json package (starting with Go 1.17).
3 years ago
exported: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int caninterface=false name=int
reflect: add support for struct types
5 years ago
int: 5
field: 1 some
compiler,reflect: fix pkgpath for struct fields
2 years ago
pkg: main
reflect: make sure null bytes are supported in tags
2 years ago
tag: "some\x00tag"
reflect: add support for struct types
5 years ago
embedded: false
reflect: add StructField.IsExported method This field was introduced in Go 1.17 and is used by the encoding/json package (starting with Go 1.17).
3 years ago
exported: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: struct caninterface=false name=point
reflect: add support for struct types
5 years ago
struct: 2
field: 0 X
compiler,reflect: fix pkgpath for struct fields
2 years ago
pkg:
reflect: make sure null bytes are supported in tags
2 years ago
tag: ""
reflect: add support for struct types
5 years ago
embedded: false
reflect: add StructField.IsExported method This field was introduced in Go 1.17 and is used by the encoding/json package (starting with Go 1.17).
3 years ago
exported: true
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int16 caninterface=false name=int16
reflect: add support for struct types
5 years ago
int: -5
field: 1 Y
compiler,reflect: fix pkgpath for struct fields
2 years ago
pkg:
reflect: make sure null bytes are supported in tags
2 years ago
tag: ""
reflect: add support for struct types
5 years ago
embedded: false
reflect: add StructField.IsExported method This field was introduced in Go 1.17 and is used by the encoding/json package (starting with Go 1.17).
3 years ago
exported: true
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int16 caninterface=false name=int16
reflect: add support for struct types
5 years ago
int: 3
field: 2 zero
compiler,reflect: fix pkgpath for struct fields
2 years ago
pkg: main
reflect: make sure null bytes are supported in tags
2 years ago
tag: ""
reflect: add support for struct types
5 years ago
embedded: false
reflect: add StructField.IsExported method This field was introduced in Go 1.17 and is used by the encoding/json package (starting with Go 1.17).
3 years ago
exported: false
reflect: implement CanInterface and fix string Index() This commit fixes two related issues: 1. CanInterface was unimplemented. It now uses the same check as is used in Interface() itself. This issue led to https://github.com/tinygo-org/tinygo/issues/3033 2. Allow making an interface out of a string char element. Doing this in one commit (instead of two) because they are shown to be correct with the same tests.
2 years ago
reflect type: struct caninterface=false
reflect: add support for struct types
5 years ago
struct: 0
field: 3 buf
compiler,reflect: fix pkgpath for struct fields
2 years ago
pkg: main
reflect: make sure null bytes are supported in tags
2 years ago
tag: ""
reflect: add support for struct types
5 years ago
embedded: false
reflect: add StructField.IsExported method This field was introduced in Go 1.17 and is used by the encoding/json package (starting with Go 1.17).
3 years ago
exported: false
reflect: implement CanInterface and fix string Index() This commit fixes two related issues: 1. CanInterface was unimplemented. It now uses the same check as is used in Interface() itself. This issue led to https://github.com/tinygo-org/tinygo/issues/3033 2. Allow making an interface out of a string char element. Doing this in one commit (instead of two) because they are shown to be correct with the same tests.
2 years ago
reflect type: slice caninterface=false comparable=false
reflect: add support for struct types
5 years ago
slice: uint8 2 2
pointer: true
nil: false
indexing: 0
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 addrable=true caninterface=false name=uint8
reflect: add support for struct types
5 years ago
uint: 71
indexing: 1
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 addrable=true caninterface=false name=uint8
reflect: add support for struct types
5 years ago
uint: 111
field: 4 Buf
compiler,reflect: fix pkgpath for struct fields
2 years ago
pkg:
reflect: make sure null bytes are supported in tags
2 years ago
tag: ""
reflect: add support for struct types
5 years ago
embedded: false
reflect: add StructField.IsExported method This field was introduced in Go 1.17 and is used by the encoding/json package (starting with Go 1.17).
3 years ago
exported: true
reflect: implement t.Comparable() This is necessary to support the context package, which is a dependency of a lot of packages.
5 years ago
reflect type: slice comparable=false
reflect: add support for struct types
5 years ago
slice: uint8 1 1
pointer: true
nil: false
indexing: 0
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 settable=true addrable=true name=uint8
reflect: add support for struct types
5 years ago
uint: 88
reflect: add support for linked lists Linked lists are usually implemented as follows: type linkedList struct { next *linkedList data int // whatever } This caused a stack overflow while writing out the reflect run-time type information. This has now been fixed by splitting the allocation of a named type number from setting the underlying type in the sidetable.
5 years ago
reflect type: ptr
pointer: true struct
nil: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: struct settable=true addrable=true name=linkedList
reflect: add support for linked lists Linked lists are usually implemented as follows: type linkedList struct { next *linkedList data int // whatever } This caused a stack overflow while writing out the reflect run-time type information. This has now been fixed by splitting the allocation of a named type number from setting the underlying type in the sidetable.
5 years ago
struct: 2
field: 0 next
compiler,reflect: fix pkgpath for struct fields
2 years ago
pkg: main
reflect: make sure null bytes are supported in tags
2 years ago
tag: "description:\"chain\""
reflect: add support for linked lists Linked lists are usually implemented as follows: type linkedList struct { next *linkedList data int // whatever } This caused a stack overflow while writing out the reflect run-time type information. This has now been fixed by splitting the allocation of a named type number from setting the underlying type in the sidetable.
5 years ago
embedded: false
reflect: add StructField.IsExported method This field was introduced in Go 1.17 and is used by the encoding/json package (starting with Go 1.17).
3 years ago
exported: false
reflect: implement CanInterface and fix string Index() This commit fixes two related issues: 1. CanInterface was unimplemented. It now uses the same check as is used in Interface() itself. This issue led to https://github.com/tinygo-org/tinygo/issues/3033 2. Allow making an interface out of a string char element. Doing this in one commit (instead of two) because they are shown to be correct with the same tests.
2 years ago
reflect type: ptr addrable=true caninterface=false
reflect: add support for linked lists Linked lists are usually implemented as follows: type linkedList struct { next *linkedList data int // whatever } This caused a stack overflow while writing out the reflect run-time type information. This has now been fixed by splitting the allocation of a named type number from setting the underlying type in the sidetable.
5 years ago
pointer: false struct
nil: true
field: 1 foo
compiler,reflect: fix pkgpath for struct fields
2 years ago
pkg: main
reflect: make sure null bytes are supported in tags
2 years ago
tag: ""
reflect: add support for linked lists Linked lists are usually implemented as follows: type linkedList struct { next *linkedList data int // whatever } This caused a stack overflow while writing out the reflect run-time type information. This has now been fixed by splitting the allocation of a named type number from setting the underlying type in the sidetable.
5 years ago
embedded: false
reflect: add StructField.IsExported method This field was introduced in Go 1.17 and is used by the encoding/json package (starting with Go 1.17).
3 years ago
exported: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int addrable=true caninterface=false name=int
reflect: add support for linked lists Linked lists are usually implemented as follows: type linkedList struct { next *linkedList data int // whatever } This caused a stack overflow while writing out the reflect run-time type information. This has now been fixed by splitting the allocation of a named type number from setting the underlying type in the sidetable.
5 years ago
int: 42
reflect: track flags when size changes from fits-in-pointer to not Fixes #3328
2 years ago
reflect type: struct
struct: 2
field: 0 A
compiler,reflect: fix pkgpath for struct fields
2 years ago
pkg:
reflect: make sure null bytes are supported in tags
2 years ago
tag: ""
reflect: track flags when size changes from fits-in-pointer to not Fixes #3328
2 years ago
embedded: false
exported: true
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uintptr name=uintptr
reflect: track flags when size changes from fits-in-pointer to not Fixes #3328
2 years ago
uint: 2
field: 1 B
compiler,reflect: fix pkgpath for struct fields
2 years ago
pkg:
reflect: make sure null bytes are supported in tags
2 years ago
tag: ""
reflect: track flags when size changes from fits-in-pointer to not Fixes #3328
2 years ago
embedded: false
exported: true
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uintptr name=uintptr
reflect: track flags when size changes from fits-in-pointer to not Fixes #3328
2 years ago
uint: 3
reflect: implement Value.Elem() for interface values
3 years ago
reflect type: slice comparable=false
slice: interface 3 3
pointer: true
nil: false
indexing: 0
reflect type: interface settable=true addrable=true
interface
nil: false
compiler,reflect: fix NumMethods for Interface type
5 months ago
NumMethod: 0
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int name=int
reflect: implement Value.Elem() for interface values
3 years ago
int: 3
indexing: 1
reflect type: interface settable=true addrable=true
interface
nil: false
compiler,reflect: fix NumMethods for Interface type
5 months ago
NumMethod: 0
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: string name=string
reflect: implement Value.Elem() for interface values
3 years ago
string: str 3
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 name=uint8
reflect: implement Value.Elem() for interface values
3 years ago
uint: 115
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 name=uint8
reflect: implement Value.Elem() for interface values
3 years ago
uint: 116
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: uint8 name=uint8
reflect: implement Value.Elem() for interface values
3 years ago
uint: 114
indexing: 2
reflect type: interface settable=true addrable=true
interface
nil: false
compiler,reflect: fix NumMethods for Interface type
5 months ago
NumMethod: 0
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: complex128 name=complex128
reflect: implement Value.Elem() for interface values
3 years ago
complex: (-4.000000e+000+2.500000e+000i)
reflect: implement New function This is very important for some use cases, for example for Vecty.
4 years ago
reflect type: ptr
pointer: true int8
nil: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int8 settable=true addrable=true name=int8
reflect: implement New function This is very important for some use cases, for example for Vecty.
4 years ago
int: 5
reflect type: ptr
pointer: true int16
nil: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int16 settable=true addrable=true name=int16
reflect: implement New function This is very important for some use cases, for example for Vecty.
4 years ago
int: -800
reflect type: ptr
pointer: true int32
nil: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int32 settable=true addrable=true name=int32
reflect: implement New function This is very important for some use cases, for example for Vecty.
4 years ago
int: 100000000
reflect type: ptr
pointer: true int64
nil: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: int64 settable=true addrable=true name=int64
reflect: implement New function This is very important for some use cases, for example for Vecty.
4 years ago
int: -1000000000000
reflect type: ptr
pointer: true complex128
nil: false
reflect: return correct name for unsafe.Pointer type For some reason, the type kind name is "unsafe.Pointer" while the .Name() method just returns "Pointer". Not sure why this difference exists, but to be able to test .Name() in testdata/reflect.go it needs to match.
3 months ago
reflect type: complex128 settable=true addrable=true name=complex128
reflect: implement New function This is very important for some use cases, for example for Vecty.
4 years ago
complex: (-8.000000e+000-2.000000e+006i)
reflect: add limited support for all type kinds This commit makes sure all Go types can be encoded in the interface type code, so that Type.Kind() always returns a proper type kind for any non-nil interface.
6 years ago
sizes:
reflect: add support for Type.Bits()
5 years ago
int8 1 8
int16 2 16
int32 4 32
int64 8 64
uint8 1 8
uint16 2 16
uint32 4 32
uint64 8 64
float32 4 32
float64 8 64
complex64 8 64
complex128 16 128
compiler: fix incorrect unsafe.Alignof on some 32-bit architectures This should fix https://github.com/tinygo-org/tinygo/issues/2643
3 years ago
offset for int64 matches: true
offset for complex128 matches: true
compiler: fix interface lowering miscompilation with reflect When using reflect, arbitrary types can be synthesized. This invalidates a few assumptions in the interface-lowering pass, that think they can see all types that are in use in a program and optimize accordingly. The file size impact depends on the specific program. Sometimes it's nonexistent, sometimes it's rather hefty (up to 30% bigger). Especially the samd21 targets seem to be affected, with a 2000-6000 bytes increase in code size. A moderately large case (the stdlib test) increases by 4%/6%/15% depending on the target. I hope that this increase could be mitigated, but I don't see an obvious way to do that.
5 years ago
type assertion succeeded for unreferenced type
extend stdlib to allow import of more packages (#1099) * stdlib: extend stdlib to allow import of more packages
4 years ago
compiler: alignof(func) is 1 pointer, not 2 This ensures that an embedded [0]func() never ends up being larger than 1 pointer, which is requried by protobuf processing code.
3 years ago
alignment / offset:
struct{[0]func(); byte}: true
extend stdlib to allow import of more packages (#1099) * stdlib: extend stdlib to allow import of more packages
4 years ago
struct tags
blue gopher
reflect: don't construct an interface-in-interface value v.Interaface() could construct an interface in interface value if v was of type interface. This is not correct, and doesn't follow upstream Go behavior. Instead, it should return the interface value itself.
3 years ago
v.Interface() method
kind: interface
int 5