Seems unfortunate, see also #44970 #43052

cc @bcmills @jayconrod

cc @matloob as well on cmd/go issues.

Sorry, but for now at least, this is working as expected in 1.16. module.CheckImportPath lists the character restrictions on import paths. Those restrictions didn't technically change in 1.16, but the go command started checking them for packages in the main module, in order to avoid surprising failures when publishing a module for the first time.

Unicode restrictions gives the rationale for the restrictions. Essentially, we're concerned that files will get different names on different file systems, and may end up overlapping or being compiled differently. As stated there, this may be relaxed in the future.

Unicode restrictions gives the rationale for the restrictions. Essentially, we're concerned that files will get different names on different file systems, and may end up overlapping or being compiled differently. As stated there, this may be relaxed in the future.

I understand, but at present, this limitation has a great probability of causing trouble to non English operating system developers. Can I change the error into a warning, or add the relevant configuration switch here

We generally avoid reporting warnings or adding configuration options if we can avoid it.

I do think we should expand the set of allowed characters though. I've opened #45549 to come up with a broader set of allowed characters that won't cause compatibility problems.

I do think we should expand the set of allowed characters though. I've opened #45549 to come up with a broader set of allowed characters that won't cause compatibility problems.

It would be great if we could expand the allowed character set. Thank you

also do this error,now back to 1.15,,,cry