Add roles declarations to allow safe coercions #9
Conversation
This file contains hidden or 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
JordanMartinez
approved these changes
Nov 17, 2020
57 tasks
thomashoneyman
approved these changes
Nov 17, 2020
|
@kl0tl Looks like CI is failing here, too, because CI isn't using the |
kl0tl
force-pushed
the
roles-declarations
branch
from
172c454 to
2eb6922
Compare
|
Thanks! |
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.
This allows terms of type
Exists fto be coerced to typeEffect gwhenCoercible f gholds, hence allowing the zero costcoerceinstead ofrunExists (wrap >>> mkExists)andrunExists (unwrap >>> mkExists)to introduce and eliminate newtypes with an existentially quantified parameter.