Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@asakaev
Copy link
Contributor

@asakaev asakaev commented Sep 19, 2019

Usually using this technique, you have to write boilerplate code.
Inspired by @mpilquist implementation.

Copy link
Contributor

@vasilmkd vasilmkd left a comment

Choose a reason for hiding this comment

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

Fun. We already have unTake implemented as a syntax class. For the sake of consistency, I'd prefer if this followed suit.

@iravid wdyt?

@asakaev
Copy link
Contributor Author

asakaev commented Sep 20, 2019

I don't get the purpose of using extension methods if we have access to sources. What is the reason?

There is only one method implemented as an extension. What makes it distinct from the others? Maybe it should be implemented as a method of a class?

@iravid
Copy link
Member

iravid commented Sep 20, 2019

Thanks @asakaev! Keeping the methods on the class as you've done is preferable (better discoverability). Let's move unTake in as well.

@vasilmkd
Copy link
Contributor

Moving unTake works as well! Thanks.

@iravid iravid merged commit 6a54361 into zio:master Sep 21, 2019
@iravid
Copy link
Member

iravid commented Sep 21, 2019

Nice work @asakaev! Thanks for reviewing @vasilmkd!

@vasilmkd
Copy link
Contributor

@iravid my pleasure. I'm willing to donate review cycles, as you call them, generously for the duration of the hackathon.

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