3 ms·
By the way, are there any projects underway to produce a library of the most common basic template functions? I'm very much looking forward to unifying some of
by majewsky 5y ago
By the way, are there any projects underway to produce a library of the most common basic template functions? I'm very much looking forward to unifying some of my most copy-pasted functions when 1.18 is out, but I would like to unify on a central library right away.
- ainar-g 5y agoIt's partially being done in the x/exp module to prototype it thoroughly before including it into the stdlib. See: * https://pkg.go.dev/golang.org/x/exp/constraints https://pkg.go.dev/golang.org/x/exp/constraints * https://pkg.go.dev/golang.org/x/exp/maps https://pkg.go.dev/golang.org/x/exp/maps * https://pkg.go.dev/golang.org/x/exp/slices https://pkg.go.dev/golang.org/x/exp/slices
- vlunkr 5y agoCool. I'd love to see this become part of the stdlib rather than competing external packages.
- newuser94303 5y agoIf it becomes part of the stdlib, the update cycle will match the language. For now, improvements will come a lot faster as an external package
- dpatterbee 5y agoI believe the goal is for stdlib packages to be added with 1.19 once they have some real-world use. For now they're in x/exp to allow changes before that release.
- shp0ngle 5y agoThey want to be able to break backwards compatibility, so they can experiment more. If they put it in stdlib, they cannot break it anymore.