Can't remember if I shared this here before, but I always thought it would be great for Elm's enforcement to also test that the existing behavior was still unchanged between versions.
Until Roc has separate tests, this isn't really applicable, but it would be cool to think about now.
Here's a POC of what I wanted in Elm, testing a new minor/patch version against a previous versions' tests.
https://github.com/matt-savvy/elm-backwards
That's interesting @Unshipped9094, what do you mean by separate tests exactly?
Happy to hear it’s not a strict enforcement, since I think that’s a point where Elm is too strict (since you are only allowed to publish a new MAJOR if you have a breaking change in some type signature, rather than any breaking change, period)
Last updated: Jul 23 2026 at 13:15 UTC