On Monday, January 20, 2020 at 12:26:38 PM UTC+1, Tamás Gulácsi wrote:
>
> Why do you want to pin to a commit when everything is in flux - develop
> locally?
Because to decide when the API is good for publication I want to use it in
1+ projects.
Since the local development period may be long,
Why do you want to pin to a commit when everything is in flux - develop locally?
The replace directive uses the current code when you declare it as a local
path, not the version specified in the "require" section!
--
You received this message because you are subscribed to the Google Groups
"go
>> Why not just the replace directive in go.mod?
>
> With the replace directive to a local module, the version is ignored and the
> go tool always use the latest commit.
How are you envisaging that local modules be addressed by commit,
given the target is a directory (where by definition only a s
On Sunday, January 19, 2020 at 11:47:30 PM UTC+1, Tamás Gulácsi wrote:
>
> Why not just the replace directive in go.mod?
With the replace directive to a local module, the version is ignored and
the go tool always use the latest commit.
Manlio Perillo
--
You received this message because you
