refactor: Migrate to prettyprinter #18
Merged
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
414owen
force-pushed
the
os/use-prettyprinter
branch
from
5125c28
to
37a9949
Compare
414owen
force-pushed
the
os/use-prettyprinter
branch
from
37a9949
to
5e79254
Compare
haskell/actions/setup is deprecated in favor of haskell-actions/setup.
abhinav
approved these changes
Apr 6, 2024
|
@abhinav thank you very much! :) |
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.
The ecosystem seems to be moving towards
prettyprinter, to the extent that it seems easier to build packages which depend onprettyprinter, rather thanansi-wl-pprint.This is a breaking change, by virtue of the removal of Pretty instances.
I think you currently have to choose between backend-specific features or a Pretty instance, with
prettyprinter.