Re:Go’s alias proposal and all my concerns of Google control...
by speps on Monday November 07, 2016 @02:23AM
(#12889464)
Good, one of Go's strength is easy refactoring given that the standard library includes its own parser and syntax packages. If something gets renamed, just write a small script to replace all references...
[ Parent
| on HN ]
Re:Go’s alias proposal and all my concerns of Google control...
by KirinDave on Monday November 07, 2016 @10:27AM
(#12891775)
But that doesn't scale at all unless you can push it back out. Aliasing and running this script both imply long term maintenance commitments, but the script is alot more invasive and requires a lot more work because its semantics are defined over the whole language as a transformer rather than as a single feature inside the compiler.
I think people suggesting a transformer script are inviting Go back into the dark pre-vendor days when every dependency got out of date rapidly and builds were "losable".
Re:Go’s alias proposal and all my concerns of Google control...
by Sphax on Monday November 07, 2016 @05:15AM
(#12889996)
It's coming back in Go 1.9
Re:Go’s alias proposal and all my concerns of Google control...
by rusht on Monday November 07, 2016 @09:59AM
(#12891501)
I thought the implementation was still up for discussion so I doubt it has been assigned a release yet, do you have a source?
Re:Go’s alias proposal and all my concerns of Google control...
by Sphax on Tuesday November 08, 2016 @05:30AM
(#12899087)
I inferred it from the comments here: https://github.com/golang/go/issues/16339#issuecomment-25852...
But of course it can still change.