Just a heads-up: I changed one of my repos URL [0], released as v0 at the moment, and bumped to v1 alongside the URL change.
Go treats v0 and v1 as equivalent, so it tries to bump from v0.x to v1.0.0 keeping the old URL. This causes errors because the `go.mod` URL isn't the same.
If you want to change the URL and you haven't reached v1, you should do it as a v2 instead, skipping v1.
It's a similar experience in Go, specially because imports are done by URL and major versions higher than v1.x are forced to change it to add a suffix `/vN` at the end.
Although this is true, any large ecosystem will have some popular packages not holding to semver properly. Also, the biggest downside is when your `>=v1` depends - indirectly usually - on a `v0` dependency which is allowed to do breaking changes.
That's an unfair characterisation of EU. Hungary and Slovakia didn't join under their current fascist governments. They weren't fascist when they joined in 2004.
Kicking them out isn't easy unless there is unanimity. Unfortunately EU requires this kind of quorum for the big decisions, which is kind of a safeguard to precisely avoid going full fascist for the whole EU due to a minority of countries.
The structure reads as LLM written. I don't mind this unless the content is utterly wrong. I was actually learning about cache-friendly data structures and I'm really interested in that cache-friendly Robin Hood hashing but now I worry it's a hallucination.
Neato! It's nice to find zserge around. He built upon the idea of my static site generator Zas [0] to create his own zs [1][2] a few years ago. I think he's still using it :)
Go treats v0 and v1 as equivalent, so it tries to bump from v0.x to v1.0.0 keeping the old URL. This causes errors because the `go.mod` URL isn't the same.
If you want to change the URL and you haven't reached v1, you should do it as a v2 instead, skipping v1.
0: https://dario.cat/mergo
reply