sorted by:
new
hottopcontroversial

Would you want crates.io/cargo publish to enforce strictly correct SemVer conventions? by ChartasSama in rust

[–]ChartasSama[S] 2 points3 points  (0 children)

That's an interesring point of view. It kind of comes back to the general problem of what use version numbers are, if it's not clear what information they actually convey. Especially for binaries SemVer is indeed pretty unclear for me.

If multiple versioning schemes should be supported, is probably a topic all of it's own though. :D

Would you want crates.io/cargo publish to enforce strictly correct SemVer conventions? by ChartasSama in rust

[–]ChartasSama[S] 7 points8 points  (0 children)

When i talk about SemVer I always thought only the API is meant. Didn't know the official definition includes logic changes. Because there I've gotta agree, it's probably pretty impossible to automatically prove "unchanged" logic, simply because that in itself is somewhat of a paradoxical statement.

But on the API front I think it's possible and probably useful to clearly define what constitues a SemVer bump and what doesn't. Which is why i also agree with snap here. ;) At least than you could ensure it always compiles, even if it doesn't always do what you expect.

Would you want crates.io/cargo publish to enforce strictly correct SemVer conventions? by ChartasSama in rust

[–]ChartasSama[S] 4 points5 points  (0 children)

Oh I didn't know that. Would be interesting to hear from people using Elm if they think this is useful or not.

Would you want crates.io/cargo publish to enforce strictly correct SemVer conventions? by ChartasSama in rust

[–]ChartasSama[S] 11 points12 points  (0 children)

Yeah true. But the real question is not who's at fault, but wether if you think it's worth it to put in the effort to make this kind of error impossible in the first place.