Can someone pls explain this? Here is the source code for

Question

Can someone pls explain this? Here is the source code for

sync.waitgroup:
https://golang.org/src/sync/waitgroup.go?s=2022:2057#L43

Why does the (T *WaitGroup) receiver not throw an error when I call it on a non-pointer type (T WaitGroup) ?

0

03.07.2021

5 ответов

10 просмотров

Justin K Автор вопроса

Akshit
As a rule of thumb, I personally use a pointer rec...

Thanks, I have been doing this too. I got confused earlier with ‘pointer/non pointer’ consideration with interfaces vs their general reference use. I have replicated a few examples and now understand this nuance much better.

0

03.07.2021

Roman Sharkov

https://play.golang.org/p/4IQzUJyw0_o a pointer-reciver just takes the pointer of the variable you're calling it on+

0

03.07.2021

Justin K Автор вопроса

Roman Sharkov
https://play.golang.org/p/4IQzUJyw0_o a pointer-r...

Thank you, I understand that. I'm going to send a playground link in a bit of what actually got me confused.

0

03.07.2021

Justin K Автор вопроса

Roman Sharkov
https://play.golang.org/p/4IQzUJyw0_o a pointer-r...

https://play.golang.org/p/YdinlQBN_0E For a moment, I mixed up subtle differences between interface and concrete types, in the context of a method receiver. (Refer to line 31 and 28. ) I mistook that for a non-pointer type, I could not call its pointer receiver (as with type interface). I know better now but please do correct me if you notice gap in my understanding. Thanks!

0

03.07.2021

Akshit · Accepted Answer

Akshit

As a rule of thumb, I personally use a pointer reciver in case I want to mutate something inside the struct. And non pointer in case I don't want to

0

03.07.2021

Похожие чаты

Can someone pls explain this? Here is the source code for

5 ответов

Похожие вопросы