#generics

Introduction Go 1.27’s introduction of method generics was billed as a game-changer,...

I came from PHP, which has no type parameter, into a Go that didn't have one either. Both languages taught the same habit: substitute discipline for the compiler. Here is the audit that found 44 copies of four functions, the generic cores they collapsed onto - reader, manager, query builder, processors, transactional handler - and the bill I pay for it.

Not sketches: the generic core that carries history for every entity in my service, the declaration that instantiates it for one domain, and a live consumer sitting on top of it that I am not proud of - it was never registered in any daemon, so cache invalidation has never run in production. Plus the question I have no answer to: how declarative should this have been?

Go 1.27 lets methods declare their own type parameters. I converted a 14-function helper package, hit the interface rule that still says no, and rever

📅 เขียนเมื่อ: กันยายน 2026 | Go 1.27 ⚠️ API/เวอร์ชันอาจเปลี่ยนแปลง —...

An audit found 44 copies of four row-reading shapes in one service. Twelve of them differed only in the text of an error wrapper. Here is the rule I replaced them with, the core they collapsed into, and what the tag-to-tag numbers did afterwards.

Introduction: The Evolution of Go and Its Philosophical Shift Go, born out of a desire for...

Go generics fill a specific blind spot: algorithms that work identically for any type. Real-world experience on patterns that work and those that make code worse.

Generics beat interfaces for some Go code and add noise to the rest. Type sets, real container and numeric examples, and the compile-time cost.

Java added generics in Java 5, and the team made a call that still echoes today: type erasure. At...

Bilingual post · Post bilíngue Jump to: English · Português English {#english} ...

It's 2026. You've watched the language wars get louder for another year. Rust keeps eating systems...