we can clearly see an OOP-language fan this is a chat for no generics enjoyers
It clearly is a chat for if x!=nil enjoyers
How are generics related to OOP?
golang has introduced generics in go1.17 if you are interested, you may want to see this article and follow this github repo (mostly follow their issue tracker to see people's proposal about new features; and if you need a new feature, you can simply create a new issue for it and go developers will add "proposal" label for it; but before doing so, search your topic to see if someone before you has already proposed that feature of not) in golang's github repo's issue tracker, there is a special label called "generics"; if you are interested in this topic this much, you can click on that label and see what's happening (and what will happen in the future) (and yes, it may not be matured yet, but it's still considered as "generics", and I really like the way it works)
Go didn't introduce generics in 1.17 They'll probably arrive in 1.18
eh, really? but I saw an issue which was in go1.17 milestone and it was related to generics (tho I can't remember where is that issue now) my bad
Erm, no. Generics are as related to OOP as high order functions mainly because GENERICS ARE HIGH ORDER FUNCTIONS THAT RUN AT COMPILE TIME, and also they have nothing to do with objects per se
Generics have been first a mere thought and then WIP for a good while by now
1.17 has them behind a flag iirc
It's in its early stages, but not yet released
Обсуждают сегодня