Re: [go-nuts] Re: Experience report on coming to Go from a C perspective

2018-02-25 Thread Jason E. Aten
On Thursday, February 22, 2018 at 3:58:25 PM UTC-6, Devon H. O'Dell wrote: > > Thanks for pointing this out; I wasn't aware of this new syntax. I > think this gets to about halfway of what I'd hope for. That said, I'd > really like to avoid needing to jump through the hoop of indirection >

Re: [go-nuts] Re: Experience report on coming to Go from a C perspective

2018-02-24 Thread Egon
Few additional possible solutions: 1. use something similar to https://github.com/awalterschulze/goderive create appropriate func. 2. some IDE / tool should be able to figure these refactorings out... or at least find the places that need to be changed. Changing a field or method name is quite

Re: [go-nuts] Re: Experience report on coming to Go from a C perspective

2018-02-22 Thread Devon H. O'Dell
Thanks for pointing this out; I wasn't aware of this new syntax. I think this gets to about halfway of what I'd hope for. That said, I'd really like to avoid needing to jump through the hoop of indirection for this. I occasionally find it hard to recognize what the type of a thing is due to heavy

[go-nuts] Re: Experience report on coming to Go from a C perspective

2018-02-22 Thread jake6502
Have you considered using the new type alias feature introduced in 1.9? Line so: https://play.golang.org/p/6HK8qcuh9UU This would allow you to change the type of the map in a singe place (the type alias) and all the *{}* or *make *would adapt appropriately. Disclaimer: I am not espousing this