This doesn't need to go through the proposal process, that's only for significant changes in the language or the standard library.

CC @jayconrod @matloob

These simple error build info is not enough to guide me to add what statement in go.mod file of main module. Meanwhile, these simple build error message does not hint to me that the problem is about replace directive missing

In general the solution to this sort of problem is not to add your own replace directive; rather, it is to fix whatever dependency has the replace directive so that it works with the same versions of other modules that everyone else uses.

I think it might be reasonable to surface the replace directives from dependencies in case of a build error involving those dependencies, but we should still report the problem as a build error, not suggest adding a replace directive.

@bcmills Thank you for your reply.

In general the solution to this sort of problem is not to add your own replace directive; rather, it is to fix whatever dependency has the replace directive so that it works with the same versions of other modules that everyone else uses.

It's true that we should fix whatever dependency has the replace directive when those dependencies are belong to us. However, sometimes we may import some 3rd party modules has some replace directives, which will make things hard.

I think it might be reasonable to surface the replace directives from dependencies in case of a build error involving those dependencies, but we should still report the problem as a build error, not suggest adding a replace directive.

Exactly, I think that build error message involving those dependencies is enough to find out what's wrong with build failure. Suggest adding a replace directive maybe mislead user, so it's better to let user decide what to do.