“//go:fix inline and the source-level inliner” by Alan Donovan — https://go.dev/blog/inliner
#golang
“Type Construction and Cycle Detection” by Mark Freeman — https://go.dev/blog/type-construction-and-cycle-detection
#golang
Go
Go
I’m glad I’m not the only one that found the idea of not reviewing code unreasonable. Beyond even finding problems or understanding the code, a key component of code review is ensuring that the code base remains maintainable over the long term.
>benchmark perf improvements
>it's slower
The SAT had the same cursive paragraph thing too when I took it. I had a similar nervous reaction!
I’m glad you have this follow up so not to anger the h2_bundle fan club.
Now you’ve learned to stick to HTTP/3 proposals. Those are much simpler than uuid.
Oh! If you like bundle, you’ll love github.com/u-root/gobus..., an awesome cursed tool for combining multiple package mains into one binary.
