3 ms·
Hm, shouldn't they first update the (most important/interesting) libraries in a fork before stabilizing generics? I mean designing a feature in a clean room is
by dathinab 5y ago
Hm, shouldn't they first update the (most important/interesting) libraries in a fork before stabilizing generics?
I mean designing a feature in a clean room is one think, but using it a the standard library would be a good way to know if they messed up the design in some way.
- spockz 5y agoYes that would be a good idea. However, they could already have a generic collection lib in the same place (branch/repo) where the generics feature is created.
- lbhdc 5y agoThis is what Rob proposes in this issue. > I propose we still design, build, test, and use new libraries for slices, maps, channels, and so on, but start by putting them in the golang/x/exp repository.