I think this is actually a bug in rsc.io/quote/v3 itself:
https://github.com/rsc/quote/blob/5d9f230bcfbae514bb6c2215694c2ce7273fc604/v3/quote.go#L6

Oh yeah: it's an intentional breakage in rsc.io/quote/v3.

Check out the commit message: rsc/quote@fe488b8#diff-43a03299a3c3fed3d8ce7b820f3aca81

Hmm, there may be another bug here, though: it's possible that in module mode we're not enforcing canonical import path comments.

I'm hitting similar issues when trying to port my v2 packages with vanity imports and // import "..." comments to a Go module:

can't load package: package mvdan.cc/sh/syntax: code in directory /home/travis/gopath/src/mvdan.cc/sh/syntax expects import "mvdan.cc/sh/v2/syntax"

You can see the full build log for 1.10.3 on Linux here: https://travis-ci.org/mvdan/sh/jobs/404138919

Building this outside of GOPATH on the latest tip works fine. I presume that 1.10 needs fixing, unless I'm missing something obvious.

I regret reminding people in the vgo-tour that canonical import paths even existed.

I used the import comment in the tour to show that if you are using them, then vgo could use that information to derive the correct 'module' line for an auto-initialized go.mod. Unfortunately, what lots of people took away instead was that using modules would mean using import comments. In fact, the opposite is true: import comments are basically obsoleted by modules.

The reason for introducing import comments was to make sure that if there were two different paths to name a package (because of custom import domain redirects) that an author could make sure all users were using the preferred name. Before that feature, there was no clear statement of the import path elements above the repository root.

With modules, we now have the clear statement we lacked before: the module statement in go.mod. Because of this, the module loading code ignores import comments entirely, and I expect that once we switch to modules we will probably deprecate them officially.

So it's working as intended that import comments are not enforced in module mode.

@mvdan, I would suggest just dropping the import comments from the v2 revs of your repo.

That makes sense - thank you for the clarification. I think we should document this well, though. The reason I was trying to make import comments work was because they were there before, and no part of the Go modules documentation told me they were to be deprecated.

So this will be a non-issue once the feature is clearly marked as deprecated :)

Because of this, the module loading code ignores import comments entirely

Which is of course less than ideal when a user operates in module mode but go gets a package that doesn't have a go.mod file yet. The import comment will be ignored, and things will tend to break in unexpected ways due to github.com/foo/bar importing example.com/foo/baz.