Thank you for answering Why does it take so long to implement generics then? There is already an instrument in playground that works fine. Why not just roll it out and improve design, if needed, in next version?
Having generics in 2021 means many projects will choose other languages in 2020, which will effectively mean 1 year of work in other language On Mon, Aug 10, 2020, 04:13 Ian Lance Taylor <i...@golang.org> wrote: > On Sat, Aug 8, 2020 at 7:51 PM <ivanivanyuk1...@gmail.com> wrote: > > > > Add support of optional syntax_version to file beginning, allow compiler > to tokenize/compile file by the compiler of syntax_version, using any > number of syntax_version-s in same project > > > > Why? Because go takes ridiculously long to implement generics, and > implementation is very likely to not be perfect or to become not perfect > when world changes. Having support of several syntaxes/compilers in same > project will allow to adapt syntax faster > > We already support something like this on a per-module basis via the > "go" line in a go.mod file > (https://golang.org/cmd/go/#hdr-The_go_mod_file). See also > > https://go.googlesource.com/proposal/+/refs/heads/master/design/28221-go2-transitions.md > . > > Ian > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CA%2BXqAJwADTgR31tg422dtn5vEYP%3DQUyzOzBtYs44mHCHZF0wSA%40mail.gmail.com.
