For my part, I see some value in maintaining a source of example solutions
to problems that generics could solve. Since I was not aware of any
resource that attempts to gather together several example implementations
in one place (and couldn't find one after a couple minutes of searching), I
decided to create one.

You can find it on GitHub at go2go-snippets
<https://github.com/kalexmills/go2go-snippets>.

For the moment, it's mostly incomplete, but even so, there's no reason not
to share it. I am hoping that the community might help to fill in some of
the gaps before I get to them. I also want to encourage submitting multiple
implementations for the same problem. Having a variety of solutions to look
at and compare can help the community learn about idioms that may and may
not be useful, and could yield some productive insights.

Feel free to also submit any generic code you've tinkered with; along with
a statement of what concrete problem it aims to solve.

I hope that having a set of concrete implementations to refer to helps to
clarify at least part of the impact of the current proposal both for the
designers and the community.

One final point deserves some mention. As the prototype evolves, some of
these examples may go out-of-date, and they may or may not be maintained.
I'm fine with that. None of the examples should be large enough on their
own that this will represent a significant loss of effort. In my view, the
benefit we would gain from even a transient set of examples will outweigh
any time invested in their creation.

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CALJzkY9zSiRdBfeQ%3DjnJJNPVU%3DX2m5oBbh07X5g7v%3D_WOuFckQ%40mail.gmail.com.

Reply via email to