If you're asking if it's okay to use a name coincidentally used in another package, then of course it is. There are plenty of third-party packages that are meant to replace standard library packages and which even use the same name (especially logging).
The only time you'll have a problem with it is if you want to name your package "context" and *also* use the official context package; then you'll have to modify the name at import time. It's always possible someone will be confused the first time they look at your source code, but we wouldn't get very far if we weren't allowed to re-use obvious, common names like context, account, request, response, etc. -- 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.
