.
>
> On Friday, 1 April 2022 at 13:30:40 UTC+1 vaastav...@gmail.com wrote:
>
>> Ok, I just tested this. I only see this behaviour with go 1.18. I tried
>> using go mod tidy with go1.17 and it worked as expected.
>>
>> On Friday, 1 April 2022 at 14:15:14 UTC+2 vaas
Ok, I just tested this. I only see this behaviour with go 1.18. I tried
using go mod tidy with go1.17 and it worked as expected.
On Friday, 1 April 2022 at 14:15:14 UTC+2 vaastav...@gmail.com wrote:
> I see this behaviour even in the presence of a main.go file in the same
> directory. T
> packages."*
>
> So I presume the warning you see is only when go mod tidy can't find any
> source code in the current directory.
>
> On Thursday, 31 March 2022 at 20:18:52 UTC+1 vaastav...@gmail.com wrote:
>
>> Here are the contents of the go.mod file
>&g
ather than "go list all" (because in that context, "all" is
> interpreted as the name of a package)
>
> On Thursday, 31 March 2022 at 16:12:24 UTC+1 vaastav...@gmail.com wrote:
>
>> Hi all,
>> I am encountering this problem where when I run `go mod tidy`,
Hi all,
I am encountering this problem where when I run `go mod tidy`, it simply
returns `go: warning: "all" matched no packages`. I get this error when I
run `go list all` as well.
I was hoping someone could help me as to why this is happening since I
haven't been able to find an explanation f
