oh, just one last point after a re-read - a great deal of what is required to implement generics, in go, does not need to change the syntax of the language, except where it concerns that CCR - (as replacing the builtin numeric types especially would lead to massive overhead in dereferencing), simply, embed error in everything, and expand error so it can store multiple state values, such as zero, just initialised, modified, nil pointers within, and so on. Again, at the centre of the implementation is going to be some form of Set.
-- 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.
