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

Use Lifted and Unlifted in #265 consistently #308

Merged
merged 1 commit into from
Jan 31, 2020

Conversation

sgraf812
Copy link
Contributor

There were a couple of places in #265 where I used UnliftedRep,
LiftedRep or even TYPE LiftedRep, an uncomfortable mixture of
assuming #203/#301 and not doing so.

@nomeata
Copy link
Contributor

nomeata commented Jan 31, 2020

@ggreif care to review? I’ll merge if you approve.

Copy link
Contributor

@ggreif ggreif left a comment

Choose a reason for hiding this comment

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

Nit: a word is duplicated before before --> before @sgraf812

Otherwise LGTM. No iftedRep found by grep.

@sgraf812
Copy link
Contributor Author

Thanks, fixed.

proposals/0265-unlifted-datatypes.rst Outdated Show resolved Hide resolved
proposals/0265-unlifted-datatypes.rst Outdated Show resolved Hide resolved
proposals/0265-unlifted-datatypes.rst Outdated Show resolved Hide resolved
proposals/0265-unlifted-datatypes.rst Show resolved Hide resolved
proposals/0265-unlifted-datatypes.rst Outdated Show resolved Hide resolved
@sgraf812
Copy link
Contributor Author

Oh boy, I should probably give it another read and pick up all the typos I can find.

@sgraf812 sgraf812 force-pushed the unlifted-data branch 3 times, most recently from 25f262b to 9af828a Compare January 31, 2020 15:28
…typos

There were a couple of places in ghc-proposals#265 where I used `UnliftedRep`,
`LiftedRep` or even `TYPE LiftedRep`, an uncomfortable mixture of
assuming ghc-proposals#203/ghc-proposals#301 and not doing so.

I also fixed a couple of typos and renamed some types to clarify.
@nomeata
Copy link
Contributor

nomeata commented Jan 31, 2020

Do you think you’ll find more or I should I merge?

@sgraf812
Copy link
Contributor Author

I fixed everything immediately obvious, so yes.

@nomeata nomeata merged commit 56c4b7f into ghc-proposals:master Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants