Hey @pombredanne and @AyanSinhaMahapatra, I have raised a PR for the replace directive, but had doubts regardings the best way to approach some of the the things, listed below. Would it be possible to share some suggestions on how to best approach these?

1. What should be the scope for the original and replaced modules? Would replace be fine for both of them or should one be require and other be replace?

2. If a package is in both require and replace directives, we will have 2 instances of the same package listed? Is that ok or is there a way to deal with that?
   For example in the go.mod of milvus (added in the PR), packages like github.com/expr-lang/expr and github.com/streamnative/pulsarctl are there both in the require as well in replace directives. This might be a very common scenario, as many a times a go developer might want to test an application with a local version or forked version of a dependency package, rather than using the original package

3. How do we deal with the replacement package if the replacement points to a local path like replace github.com/milvus-io/milvus/pkg => ./pkg ?
   `