Quoting Steven Wiley (2018-11-05 22:12:40)
> And let's face it. Templates, operator overloading, and talk of
> generics has swirled around golang since its inception. Separating the
> template/generic/operational overload step from the core language via a
> pre-compile step� is one way to get the ball rolling. Risks? Yes,
> bifurcation of the language I guess, but on the other hand the core of
> go remains pure. Thoughts anyone?
+1 for gaining some experience to move the discussion forward. The
approach you suggest closely mirrors this:
https://github.com/albrow/fo
..which was brought up in another thread.
---
As an aside, C++ templates and generics as specified in the draft (and
most other designs that have been floated) are really entirely different
beasts; Emily Maier wrote a post (linked from the feedback wiki) that
picks this apart:
https://emilymaier.net/words/getting-specific-about-generics/
--
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].
For more options, visit https://groups.google.com/d/optout.
