go: fix ambiguous import when using a module without a dot #7979
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to a bug in Go 1.20 (see golang/go#61873), when importing a module without a dot in it, we get:
This issue was fixed in Go 1.20.8 which was just released. By using
go1.20.8
as a toolchain for anything <= 1.20, we still cover the use case introduced in #7884, but we also avoid this bug.go1.20.8
is a valid toolchain. For Go 1.20, onlygo1.20
is a valid version forgo
directive ingo.mod
.