Re: [go-nuts] Clarification on code snippet

2023-08-04 Thread alchemist vk
Thank you Axel and burak for clarification. Now I am able to understand the syntax. Thank you again. With regards, Venkatesh On Fri, Aug 4, 2023 at 10:28 PM Axel Wagner wrote: > Another relevant section is Calls (emphasis > mine): > >> A method call x.m() is val

Re: [go-nuts] Clarification on code snippet

2023-08-04 Thread 'Axel Wagner' via golang-nuts
Another relevant section is Calls (emphasis mine): > A method call x.m() is valid if the method set of (the type of) x contains > m and the argument list can be assigned to the parameter list of m. *If x > is addressable and &x's method set contains m, x.m() is shor

Re: [go-nuts] Clarification on code snippet

2023-08-04 Thread burak serdar
On Fri, Aug 4, 2023 at 10:33 AM alchemist vk wrote: > Hi folks, > In below code, I am invoking receiver api show() via a simple uInteger > type variable instead of pointer, by which it expects to be invoked . Go > being strict with type casing and I was expecting a compiler error. But to > my s

[go-nuts] Clarification on code snippet

2023-08-04 Thread alchemist vk
Hi folks, In below code, I am invoking receiver api show() via a simple uInteger type variable instead of pointer, by which it expects to be invoked . Go being strict with type casing and I was expecting a compiler error. But to my surprise, it compiled and executed successfully. Can you folks p