You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cmd/compile complains if an import path contains a space character. More so, it also complains if a package path (import path after resolving it) contains a space character. This seems overly zealous.
For instance, for a small experiment, I had put two .go files main.go and lib.go in a local directory that happens to be under my Google Drive directory, with the main package containing the local import "./lib". Because this resolves to an absolute path containing "Google Drive" as a component, the import gets rejected.
It's probably useful to reject arbitrary Unicode spaces, but a regular blank ' ' (0x20) character should be ok. Independent of Google Drive, on OS X it is not uncommon to have blanks in folder names.
The text was updated successfully, but these errors were encountered:
griesemer
added
the
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
label
May 10, 2017
The spec forbids the import path containing a space and I don't think that should change. What you're asking for is the fully-qualified path name to be allowed to have spaces, and that seems fine.
rsc
changed the title
cmd/compile: "import path contains space character" overly zealous
cmd/compile: "import path contains space character" for imports without spaces
May 22, 2017
Fixing this (but still disallowing actual imports with actual spaces) seems fine.
rsc
added
the
NeedsFix
The path to resolution is known, but the work has not been done.
label
May 22, 2017
griesemer
removed
the
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
label
May 22, 2017
cmd/compile
complains if an import path contains a space character. More so, it also complains if a package path (import path after resolving it) contains a space character. This seems overly zealous.For instance, for a small experiment, I had put two .go files
main.go
andlib.go
in a local directory that happens to be under myGoogle Drive
directory, with themain
package containing the local import"./lib"
. Because this resolves to an absolute path containing"Google Drive"
as a component, the import gets rejected.It's probably useful to reject arbitrary Unicode spaces, but a regular blank
' '
(0x20) character should be ok. Independent of Google Drive, on OS X it is not uncommon to have blanks in folder names.The text was updated successfully, but these errors were encountered: