Lessons learned

The number one question I, and almost certainly many others, had/have on their mind regading Go generics is When should I, if ever, consider adopting this new language feature, in both greenfield and brownfield projects?

The answer, of course, is not a simple one. That is why this repository exists — it represents the journey one engineer took to try and understand generics in Go and where and how they can help developers, development, and deliveriables.

• Generics are suited for container patterns: container patterns are finally sorted
• Generics can improve performance by eliminating boxing: get rid of the empty interface
• Marshal/unmarshal patterns will not immediately benefit: boxing anywhere is still boxing
• Impact to build times & file sizes is negligible (so far): watch that compiler go!

Next: Container patterns