sry, might be may fault.
Sorry, that might be my fault. What you observed from the go mod why that
could be related to this issue: https://github.com/golang/go/issues/27900?
在2024年7月18日星期四 UTC+8 11:36:24<王旭东> 写道:
> Hi,
>
> It seems there might be a misunderstanding regarding the go mod why
> c
Hi,
It seems there might be a misunderstanding regarding the go mod why
command. Please note that any transitive dependencies will not be displayed
in the output. For instance, x/exp/shiny could be a transitive dependency
of a direct dependency in your main module, which is why you see the
m
x/mobile isn't just for bindings, it also has some support for more
full fledged apps, see https://pkg.go.dev/golang.org/x/mobile/app
It seems natural to require some rendering support for that.
- sean
On Wed, Jul 17, 2024 at 4:42 PM Alvaro Crespo
wrote:
>
> Hi!
>
> Sadly, "go mod why" doesn't r
Hi!
Sadly, "go mod why" doesn't really work for gomobile (
https://cs.opensource.google/go/x/mobile) and its dependencies since they
are technically not used in my library/package. They are used at build time
to generate language bindings that make it possible to call Go functions
from Java and Ob
Understood! I appreciate all your help.
@Axel Wagner
@Jason Phillips
@Ian Lance Taylor
Thanks again!
Xudong
在2024年7月17日星期三 UTC+8 14:02:07 写道:
> Hi,
>
>> However, I would like to point out that selector rule 3 states:
>>
>> As an exception, if the type of x is a defined pointer type and (*x).