fix: update stackage resolver to lts-22.11 for build compatibility #129
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Avoided not being registered in stackage due to the following error. > ``` > - aws-lambda-haskell-runtime < 0 # tried aws-lambda-haskell-runtime-4.1.2, but its *library* requires the disabled package: safe-exceptions-checked > ``` > > <https://github.com/commercialhaskell/stackage/blob/fb2a50c986c1dab18c5aeef5bf1e12eadcbb37f3/build-constraints.yaml#L6267C1-L6267C156> The [safe-exceptions-checked](https://hackage.haskell.org/package/safe-exceptions-checked) library was deprecated, causing it not to build. It has an old list of dependencies, so I tried adding it to `extra-deps` and found that transformers, etc. require a large number of out-of-stackage-managed dependencies, causing it not to build. I could not find any other good-looking check-exception library. Having no choice I decided to remove the check exception mechanism itself. I believe that it should not contain any destructive changes. The removal of the check exception feature changes the type signature, but does not change the behavior, so it is not broken unintentionally. It is also sufficient for the user to remove the type signatures if they have been written.
|
Thanks a lot! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Avoided not being registered in stackage due to the following error.
The safe-exceptions-checked library was deprecated, causing it not to build.
It has an old list of dependencies,
so I tried adding it to
extra-depsand found that transformers, etc. require a large number of out-of-stackage-managed dependencies, causing it not to build.I could not find any other good-looking check-exception library. Having no choice I decided to remove the check exception mechanism itself.
I believe that it should not contain any destructive changes. The removal of the check exception feature changes the type signature, but does not change the behavior,
so it is not broken unintentionally.
It is also sufficient for the user to remove the type signatures if they have been written.