A quick note on an FAQ about Go generics
Constraining Complexity in the Generics Design
A supplementary post to my GopherConAU 2023 talk of the same title.
Cleanly merge git repositories
I describe how I did a clean, four-way merge of git repositories.
Operator constraints in Go
I describe four ways to express constraints for operators in generic Go code and the trade-offs involved.
Calculating type sets is harder than you think
I try to explain why the problem of calculating the exact contents of a type set in Go is harder than it might seem on the surface.
Parametric context
Go’s Context.Value is controversial because of a lack of type-safety. I design a solution for that based on the new generics design draft.
A bird's eye view of Go
I provide a very high-level overview of what Go-the-language means vs. Go-the-ecosystem vs. Go-an-implementation. I also try to provide specific references to what documentation is most useful for what purpose.
Using roughtime as a "cryptographic notary"
Roughtime can be (ab)used for Trusted Timestamping. I wrote a simple tool as a PoC
Scrapping contracts
I describe a way to simplify the generics design. The ideas are not particularly novel and have been expressed to various degrees by other people as well. I hope to provide a more complete view of the design though.
Why doesn't Go have variance in its type system?
I explain what co-, contra- and invariance are and what the implications for Go’s type system would be. In particular, why it’s impossible to have variance in slices.