Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removed Shaped instance for Rep #3734

Merged
merged 1 commit into from
Sep 25, 2023

Conversation

MaximilianAlgehed
Copy link
Collaborator

Description

and replace its uses with TypeRep based instances

Checklist

  • Commit sequence broadly makes sense and commits have useful messages
  • New tests are added if needed and existing tests are updated
  • When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
    versioning process.
  • The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
  • All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
  • Code is formatted with fourmolu (use scripts/fourmolize.sh)
  • Cabal files are formatted (use scripts/cabal-format.sh)
  • hie.yaml has been updated (use scripts/gen-hie.sh)
  • Self-reviewed the diff

@MaximilianAlgehed
Copy link
Collaborator Author

It would be good to get the input of @lehins and @TimSheard on this one

@MaximilianAlgehed MaximilianAlgehed force-pushed the PR-typerep-remove-shaped branch 3 times, most recently from 7271448 to 375e2a9 Compare September 21, 2023 14:28
Copy link
Contributor

@lehins lehins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another amazing simplification. Perfect!!

Would be nice to @TimSheard review on this as well, however.

@MaximilianAlgehed
Copy link
Collaborator Author

@lehins there appear to be some flaky tests. Should we log these somewhere to make sure someone can go back and fix them at some point?

@lehins
Copy link
Contributor

lehins commented Sep 25, 2023

Should we log these somewhere to make sure someone can go back and fix them at some point?

No point. Everyone knows about it, so it is just a matter of time and priority till we get to it.

@lehins lehins merged commit f4d4d12 into IntersectMBO:master Sep 25, 2023
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants