I'd like to see changes to the standard library. Things that many people agree should be fixed but thwarted by go1 compat. The list is long and this mailing list is riddled with them. Possibly weeding out the standard library, kicking stuff to /x/.
I'd provide generics through preprocessors wrapping the go toolkit. Most of everything needed is already provided in /src/go. The hard works already been done by the go team. A few interesting ideas come across this mailing list, but that is it, just ideas. On Saturday, June 11, 2016 at 4:31:06 PM UTC-4, charr...@gmail.com wrote: > > Document: > https://docs.google.com/document/d/1kAc6Hn89j1aspqBdeywP0X3IvVr0P4xrOZqYr0yYgNg/edit?usp=sharing > > The project is currently stuck the following things. > swapping of generic variables. - a must have, for sort &heap obviously. > To operate on arbitrary slices not just slices of arbitrary pointers. > > The generic return is another nice to have thing, but can be emulated by C > inspired double pointer argument. > > It's time to look for new goals, maybe do some map[anything]struct{} set > thing. Various channels and merging > multiple channels with same values into one channel and other stuff is > another area ripe for exploration. > > What do you need to be added to the Go language? > -- 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.
