Arnaud,
GODEBUG=gotypesalias=1 was not redundant in my command. It was used to
suppress go vet error checking.
peter
On Sunday, August 25, 2024 at 5:30:25 PM UTC-4 Arnaud Delobelle wrote:
> Hi Peter,
>
> Thanks for mentioning gotypesalias. Looking into that, I see that the
> go1.23 release n
Arnaud,
My local devel example version,
go version devel go1.24-96d8ff00c2 Sat Aug 24 00:51:40 2024 +
Your Go Playground devel example version,run at at 2024-08-25
23:38:42.008121446 + UTC, is earlier,
devel go1.24-b6f05cc333 Tue Aug 20 13:39:19 2024 +
peter
On Sunday, August 25,
Hi Peter,
Thanks for mentioning gotypesalias. Looking into that, I see that the
go1.23 release notes mention that:
By default, go/types now produces Alias type nodes for type aliases.
This behavior can be controlled by the GODEBUG gotypesalias flag. Its
default has changed from 0 in Go 1.22
Guys, does anyone have a good resource about this topics
* CPU Architecture and Multi-Core Processors
* Operating System (OS) Fundamentals
* Process Scheduling
* Concurrency and Parallelism
* Context Switching
* Resource Management
* Performance Optimization
--
You received this message because y
Arnaud,
$ go version && go run alias.go && go vet alias.go
go version devel go1.24-96d8ff00c2 Sat Aug 24 00:51:40 2024 +
linux/amd64
b = {X:0xc00011c190 Y:0xc00011c1a0}
$
Or
$ go1.23 version && go1.23 run alias.go && GODEBUG=gotypesalias=1 go1.23
vet alias.go
go version go1.23.0 linux/amd
