cmd/go: should 'go mod init' suggest (or run) 'go mod tidy'? #41712
Description
(This issue is a follow-on to #40728, based on a discussion with @dr2chase.)
Now that we're defaulting to -mod=readonly, users who create a module from existing source code will generally need to run go mod tidy before they can actually build the packages in the module.
- Should
go mod initcheck for source files and suggest that command? - Should
go mod initgo ahead and tidy the module itself? (We don't know whether the user intends to prune out some nested modules before tidying, but nested modules should be rare anyway.)