-
Notifications
You must be signed in to change notification settings - Fork 38
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
Unexpected behavior using group-by and post-combine together #10
Comments
Hmm, yeah that is a tough one, because often you do want the post-combine to operate on the results of the group-by, but your confusion is certainly legitimate! The easy workaround here is |
One problem with the workaround is that you quickly end up with transformations that doesn't compose. An example is trying to use
|
That's a great objection. Can you find a coherent way to fix it? I'd love to put time into this right now but I've got some other things going on. Happy to see a PR though! |
I'll give it a try. My best bet is changing
What's your feelings on that approach? |
And another example with post-combine at different stages
|
kasperlanger's solution seems neat (a pathetic "me to" until I wrap my head around Tesser enough to produce a PR). |
I was hoping to extend the
group-by
example with a(post-combine inc)
like thisHowever it raises an exception because the post-combine is added to the top of the fold and
inc
doesn't like to post-combine the group-by result.The text was updated successfully, but these errors were encountered: