November 2017
Intermediate to advanced
670 pages
17h 35m
English
This is what the same block of code might look like if Go supported generics:
var cars = Slice<Car>{ Car{"Honda", "Accord", 3000}, Car{"Lexus", "IS250", 40000}, Car{"Toyota", "Highlander", 3500}, Car{"Honda", "Accord ES", 3500}, } fmt.Println("cars:", cars)
Looking at this code block from a lazy programmer's perspective, if Go supported generics, we'd have to type two extra characters, < and >.
It looks like the biggest feature of generic code support has just been neutralized. When we consider this information along with the functions we get for free with gen and the fact that the performance hit is guaranteed to occur at compile time (rather than runtime), it makes Go's direct support of generics seem like a benefit ...