You mean let modules specify the minimum Go version required to build them? Or perhaps to run them too?

Would this be just a major version like 1.9, or a full version like 1.9.2?

Also note that this is somewhat possible with build tags already, such as // +build go1.9. You can make it so that a package doesn't build with older versions, or even that it only builds with a particular major versison of Go like 1.10. This is what GopherJS does: https://github.com/gopherjs/gopherjs/blob/master/compiler/version_check.go

Hello @mvdan
I can't really tell the difference between the two (build and run) as to me you don't need Go to run compiled software. I think it would be a good idea to be able to fix a full version just in case the project needs a fix that has been implemented in a minor release.

That's right it would actually be the same as // +build go1.9 but managed at the module level, so it's easier to manage.

Wouldn't this lead to something like a version manager ? (ala ruby version manager ) 👎

Looks like this is duplicate of #23969.

You're right @rajender, thanks for noticing.