On Sat, Oct 27, 2018 at 3:31 AM, <alan.f...@gmail.com> wrote: > > Both the above are also 'take it or leave it' approaches. Either you can use > the new keywords as such or you can use them as ordinary identifiers - you > can't do both in the same package which my suggestion would allow.
That is an interesting feature but I don't think it's a necessary one. It's important that we be able to continue to compile existing code that uses identifiers that are now keywords. But it's not important that we permit that code to start using the keyword without renaming the identifier. Keywords always start with a lowercase letter, and so the corresponding identifiers are never exported. It's always possible to stop using an unexported identifier without breaking any other packages. So if you want to start using a keyword, stop using the identifier, by renaming the existing uses. That seems like a clear and reasonable requirement for moving forward to a new language version. We can even provide a `go fix` hook for it. 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. For more options, visit https://groups.google.com/d/optout.
