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
{{ message }}
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
Does this issue reproduce with the latest release?
Yes
What did you do?
cue mod init blah
What did you expect to see?
No error
What did you see instead?
invalid host name "blah"
In Go, first-elements in a module that do not include a dot are, in general, reserved for the standard library and the Go toolchain (see golang/go#37641 and golang/go#32819).
golang/go#37641 is about reserving certain names as "special" but in general go mod init blah is allowed. We should do the same for cue mod init
The text was updated successfully, but these errors were encountered:
It won't allow imports of other packages int he main module, indeed. But these kinds of throwaway modules are only ever single-package things.
It's really only laziness that caused me to raise this issue, because typing .com is apparently too hard for me!
But I take your point - it introduces a potentially sharp edge for someone who is new to CUE, where really we don't need one. Keeping it strict is certainly not a problem.
What version of CUE are you using (
cue version
)?Does this issue reproduce with the latest release?
Yes
What did you do?
What did you expect to see?
No error
What did you see instead?
In Go, first-elements in a module that do not include a dot are, in general, reserved for the standard library and the Go toolchain (see golang/go#37641 and golang/go#32819).
golang/go#37641 is about reserving certain names as "special" but in general
go mod init blah
is allowed. We should do the same forcue mod init
The text was updated successfully, but these errors were encountered: