Indeed it's a form of package/block level code-specialization, so called generics.
There is a proposal for package level generics by me too. My main concern here was to have this feature without invalidating current Go code bases, by allowing the rebinding of Type Aliases <https://docs.google.com/document/d/1vrAy9gMpMoS3uaVphB32uVXX4pi-HnNjkMEgyAHX4N4/edit#heading=h.3hz723usuzv2> . For block level generics - as suggested at the first post - there might be some substantial changes needed to be made to the language - except for the last form: Interface Receivers with Original Types, which allows to not touch current Go code bases. All in all Go is a fantastic tool with it's own merits. On Saturday, February 17, 2018 at 6:25:58 AM UTC+3:30, Mandolyte wrote: > > I think this falls into a variation of package level generics. > > Look over the document below and see if there is any changes you would > recommend. > > > https://docs.google.com/document/d/1vrAy9gMpMoS3uaVphB32uVXX4pi-HnNjkMEgyAHX4N4/edit?usp=drivesdk > > Thanks for sharing! > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
