No doubt, but it also increases the cognitive load at the call site - which is sort of against Go’s desire for explicitness. On Jan 15, 2026, at 5:38 PM, Mike Schilling <[email protected]> wrote: -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/0AFDB5C9-475C-43D9-8AC3-258619750986%40ix.netcom.com. |
- [go-nuts] Scope of variable redeclarations 'Brian Candler' via golang-nuts
- [go-nuts] Re: Scope of variable redec... 'Brian Candler' via golang-nuts
- [go-nuts] Re: Scope of variable r... 'Brian Candler' via golang-nuts
- Re: [go-nuts] Re: Scope of va... Robert Engels
- Re: [go-nuts] Re: Scope o... Jan Mercl
- Re: [go-nuts] Re: Sc... Robert Engels
- Re: [go-nuts] Re... Jan Mercl
- Re: [go-nuts... Robert Engels
- Re: [go-nuts... Mike Schilling
- Re: [go-nuts... Robert Engels
- Re: [go-nuts... Mike Schinkel
- Re: [go-nuts... Robert Engels
- Re: [go-nuts... Patrick Smith
- Re: [go-nuts... 'Brian Candler' via golang-nuts
- Re: [go-nuts] Scope of variable redec... Def Ceb
- Re: [go-nuts] Scope of variable redec... Jan Mercl
