In my previous blog packages.Load jitters, I said the jitters are caused by too many go routines are spawned so synchronization takes a lot of times.
However, at the beginning I thought the Lock in sync.Once costs a lot, so I tried to replace sync.Once with Mutex+Chan. The result is the sync.Once is still better.
In CL 614975, I have migrated deprecated loader from ssa package. However, miller has reported the tests became extremely slows. In an operation-system with a slow file system, such as plan9, the test slowed by more than 50x.
Oops, a un-intentional change:( I have submitted a CL to load 300+ packages by packages.Load once instead of loading them many. Alan thought it's a bravo change:)
Moreover, when I involved to investigate why the packages.Load slows so much, I have learned a lot. This blog records how I investigate them.
Go compiler and linker helps you to link a go function with an asm implementation. However, the unexported functions are global, which means that if you duplicate some asm files and compile, go may complain to you.
This is a blog for Go toolchains, I will try to explain what is toolchain, how to use it and why Go needs it.
This blog try to introduce the go list command and brief a refinement at go1.16. Moreover, we will explore the differences between go list -m all and go list all, and answer question why some of the module from go list -m all cannot be found by go mod why.
Finally, we will see the x/mod package and when it's useful.