-
Notifications
You must be signed in to change notification settings - Fork 18k
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
x/vgo: module path contains non-final version element v1 #23960
Comments
/cc @rsc |
I guess this issue is loosely related to #24119 (where an alternative syntax is being discussed.) but I must say I am not completely sure I understand the underlying reason for this check in the current vgo source code. is it because if we were to allow an import path with something that looks like a version then one would have to check for inconsistencies? (checking for inconsistencies looks rather easy from a 10,000 ft overview... :P) |
hi there, any news? right now we are a bit in the dark :) |
I was hit by this today trying to build https://github.com/decomp/decomp using vgo.
|
@rsc I'm pretty disappointed that this has gained no reply given the long time given and that the vgo proposal has been accepted. The absence of an answer leaves us in a difficult position of now knowing what we should do; do we step out and break all our clients or do we wait an hope that a decision is made that allows us to retain our current import paths is made. |
Sorry about leaving you hanging. I intend to make sure you can keep your import paths. |
Change https://golang.org/cl/114435 mentions this issue: |
Thanks, Russ, |
To confirm, with this change the |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes.
What operating system and processor architecture are you using (
go env
)?What did you do?
The text was updated successfully, but these errors were encountered: