I know this is probably too late.
Could it be possible that some new additions to the stdlib
could be marked unstable like parts of the testing package
and thus not covered by the Go 1 compatibility guidelines?
I am worried that some of the bits in go/* and especially
go/types are found to be non-optional in the future.
Fixing them will be painful if they are subject
to the compatibility guidelines.
- Taru Karttunen
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@example.com.
For more options, visit https://groups.google.com/d/optout.