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

Update CP437.hs #11

Closed
wants to merge 2 commits into from
Closed

Update CP437.hs #11

wants to merge 2 commits into from

Conversation

michaelt
Copy link
Contributor

@michaelt michaelt commented Mar 5, 2016

One is supposed to accumulate a builder with a right fold. https://www.reddit.com/r/haskell/comments/35udfy/fixing_an_aeson_performance_bug_sometimes_the_old/cr94pdj
I skipped that with this attempt, which unfolds the text directly. It seems 10 or more times as fast if I send /usr/share/dict/words through it. unfoldr is a pretty strong function with text since it is basically just replicates the stream representation. But maybe there is something better.

One is supposed to accumulate a builder with a right fold. https://www.reddit.com/r/haskell/comments/35udfy/fixing_an_aeson_performance_bug_sometimes_the_old/cr94pdj 
I skipped that with this attempt, which unfolds the text directly. It seems 10 or more times as fast if I send /usr/share/dict/words through it. `unfoldr` is a pretty strong function with text since it is basically just replicates to the stream representation. But maybe there is something better.
@mrkkrp
Copy link
Owner

mrkkrp commented Mar 5, 2016

Great catch. Please squash the commits together and we will be ready to merge.

@michaelt
Copy link
Contributor Author

michaelt commented Mar 5, 2016

Sorry I think I didn't understand that I was making an independent patch-2 via the github interface. I take it the other pull request layers them correctly.

@mrkkrp
Copy link
Owner

mrkkrp commented Mar 5, 2016

I just asked you to make one single commit form the two. Nevermind, I will squash them and apply from this PR myself. The second PR is of no use (it's identical anyway) — so I'm closing it.

@michaelt
Copy link
Contributor Author

michaelt commented Mar 5, 2016

Oh thanks! What I did via the github interface ended up being more complex than what I would have done otherwise, which itself involves a rather narrow supply of git skills.

@mrkkrp
Copy link
Owner

mrkkrp commented Mar 5, 2016

Applied as c108d12. Thank you!

@mrkkrp mrkkrp closed this Mar 5, 2016
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.

None yet

2 participants