You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is sometimes easier to use the typedef type and then unpack instead of using the long, uncommonly used underlying structure name. In my case it is any instead of interface {} because it's also easier on the type parser and I don't need to wait for the type selection drop down to appear before hitting enter.
I figure this is pretty straightforward so I just nuked the template on my phone.
Edit: ok maybe there is a bug too because I can't unpack interface {} either even though it is a struct. No nevermind, it too is a typedef. I guess this shows my point 😂
The text was updated successfully, but these errors were encountered:
It is sometimes easier to use the typedef type and then unpack instead of using the long, uncommonly used underlying structure name. In my case it is
any
instead ofinterface {}
because it's also easier on the type parser and I don't need to wait for the type selection drop down to appear before hitting enter.I figure this is pretty straightforward so I just nuked the template on my phone.
Edit: ok maybe there is a bug too because I can't unpack
interface {}
either even though it is a struct. No nevermind, it too is a typedef. I guess this shows my point 😂The text was updated successfully, but these errors were encountered: