-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/go: add release note for rejection of non-ASCII import paths in module mode #43052
Comments
This slightly change "panic utf8" output. Package path with unicode is officially not supported in go1.16. It was only mostly working before but with go1.16 it'll be hard broken. golang/go#43052 Tested with go @ tag go1.16beta1. Confirmed the package do not compile without this fix.
This appears to disagree with the current language spec:
I have a main package |
@jamie-digital You bring up a subtle issue: the changes that we made don't affect the compiler, but just the go command and its build system. And there are other restrictions that the build system places above those in the compiler. But I agree that it may be confusing that there are two different sets of restrictions. |
Change https://golang.org/cl/282194 mentions this issue: |
@matloob Thanks for the clarification, that makes sense. It would be really helpful to have a clear set of rules the go command will accept. |
@jamie-digital Module paths and versions is a list of restrictions on module paths. File path and size constraints is a list of restrictions on file and directory names within a module. |
@jayconrod Thanks, those are really useful references. It's worth noting that although golang.org/x/mod/module.CheckPath doesn't allow the '+', the Module paths and versions section does:
|
For |
Probably we should remove |
Change https://golang.org/cl/282512 mentions this issue: |
@bcmills I sent CL 282512 to remove |
Go 1.16 will no longer accept "+" as a character in a module or import path. Amend the module docs to reflect that change. Fixes golang/go#31376 For golang/go#43052 Change-Id: Ie0b58888cf5023c69f112dcc32137fc69af6c659 Reviewed-on: https://go-review.googlesource.com/c/website/+/282512 Trust: Michael Matloob <[email protected]> Run-TryBot: Michael Matloob <[email protected]> TryBot-Result: Go Bot <[email protected]> Reviewed-by: Jay Conrod <[email protected]> Reviewed-by: Bryan C. Mills <[email protected]>
In CL 251878 (for #29101), we tightened up the import-path check in module mode so that it now disallows all non-ASCII package import paths, not just non-ASCII module paths (see #29101 (comment)).
Although we believe the number of affected packages to be very small, we should add a release note for this change so that users can easily verify that the change was intentional (see #43035).
CC @jayconrod @matloob @maruel
The text was updated successfully, but these errors were encountered: