Introduce version bounds for dependencies #233
Comments
ivanperez-keera
added a commit
that referenced
this issue
Oct 3, 2022
The cabal file in Yampa does not specify upper bounds on dependencies. This is bad practice and should be considered a bug. It is currently limiting or endangering an update to a dependency, which would likely break packages created by Yampa users. This commit introduces version bounds for all dependencies of Yampa, all tests, and all executables/demos.
ivanperez-keera
added a commit
that referenced
this issue
Oct 3, 2022
ivanperez-keera
added a commit
that referenced
this issue
Oct 3, 2022
The cabal file in Yampa does not specify upper bounds on dependencies. This is bad practice and should be considered a bug. It is currently limiting or endangering an update to a dependency, which would likely break packages created by Yampa users. This commit introduces version bounds for all dependencies of Yampa, all tests, and all executables/demos.
ivanperez-keera
added a commit
that referenced
this issue
Oct 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The cabal file in Yampa does not specify upper bounds on dependencies. This is bad practice and should be considered a bug.
We are currently considering a change to a library (see ivanperez-keera/dunai#298 for details) but, if we introduce that change, then Yampa would break (affecting currently released versions). If we had a constraint on the upper bounds of
simple-affine-space, then this would not happen: we could just bump the major.The text was updated successfully, but these errors were encountered: