3 ms·
Nothing's physically stopping you breaking backwards compatibility without using a new import path if you want to. You might piss off your users but if they don
by IshKebab 7y ago
Nothing's physically stopping you breaking backwards compatibility without using a new import path if you want to. You might piss off your users but if they don't care then go for it.
- grey-area 7y agoDoesn’t the go tooling mandate this if you are >= v2.0? The rest of mod looks fine but tying paths to major version changes was a mistake IMO.