3 ms·
So, if I want to use the new code in v2 for my v1 legacy consumers, would I let v1 (or a new v1.1) depend on v2, and wrap the new hi-method passing in a default
by e12e 8y ago
So, if I want to use the new code in v2 for my v1 legacy consumers, would I let v1 (or a new v1.1) depend on v2, and wrap the new hi-method passing in a default parameter of "en" for language?
Or is my only "supported" option to push consumers to the new major version - with the possible bit-rot of the old code?
[ed: that is manual backport fixes/improvements to a v1.x version]
- ainar-g 8y agoRuss has explicitly written that yes, redefining v1 in terms of v2 is not only the way to go, but in the future it might help automatise the switch to v2 with the "go fix" command. See https://research.swtch.com/vgo-import https://research.swtch.com/vgo-import, section "Automatic API Updates".