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

Simplify everything by making Has into the class, and getting rid of … #35

Merged
merged 9 commits into from
Nov 17, 2022

Conversation

cgibbard
Copy link
Contributor

@cgibbard cgibbard commented Jul 9, 2020

…the ConstraintsFor type family

README.md Show resolved Hide resolved
@int-e
Copy link
Contributor

int-e commented Jul 20, 2020

I'm happy to report that lambdabot (which uses constraints-extras via dependent-sum) can still be compiled with this change.

This is kind of expected. Code that relies only on Has constraints and uses Template Haskell for deriving the instances should not break.

@Ericson2314
Copy link
Member

Ericson2314 commented Jul 20, 2020

I don't like this change, there is fancy stuff I want to do with quantified constraints that this will break. The sort of thing I started implementing in #17.

# Conflicts:
#	src/Data/Constraint/Extras.hs
#	src/Data/Constraint/Extras/TH.hs

This merge also involved a bunch of re-documentation and I extended the README to test the code for handling type families.

-- | \"Primed\" variants (@ConstraintsFor'@, 'argDict'', 'Has'',
Copy link
Contributor

Choose a reason for hiding this comment

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

Although ConstraintsFor' goes away, it might be nice to say what "primed" variants and "V" variants of things mean.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I do, just in the documentation for those things. But I can document this type synonym as well.

@o1lo01ol1o o1lo01ol1o mentioned this pull request Feb 4, 2021
@ali-abrar
Copy link
Member

@cgibbard can you resolve the conflicts? I don't care about travis, but we should make sure our CI and the actions from #50 pass.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants