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 eager parameters when by-name is not necessary #8

Merged
merged 1 commit into from
May 20, 2022

Conversation

joroKr21
Copy link
Member

@joroKr21 joroKr21 commented May 26, 2021

😄

@joroKr21 joroKr21 marked this pull request as ready for review May 26, 2021 17:12
@joroKr21 joroKr21 requested a review from milessabin May 26, 2021 17:12
@milessabin
Copy link
Member

Hmm ... they really should be necessary ... I need to dig in to why the seem not to be.

@milessabin milessabin self-assigned this May 27, 2021
@joroKr21
Copy link
Member Author

I think it's Gen.derive which takes functions with lazy parameters, no?

@TimWSpence
Copy link
Member

Hmm ... they really should be necessary ... I need to dig in to why the seem not to be.

This is something that I've been meaning to look into for a while - I've never seen anything fail (even for recursive data structures) due to strict given instances

@joroKr21
Copy link
Member Author

@milessabin what should we do with this PR?

@joroKr21
Copy link
Member Author

I'm gonna merge this - it's only tests anyway 😄

@joroKr21 joroKr21 merged commit e7ea53b into typelevel:main May 20, 2022
@joroKr21 joroKr21 deleted the eagerness branch May 20, 2022 06:51
@milessabin
Copy link
Member

Sorry I should have replied earlier ... 👍

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.

3 participants