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

Extremely slow curry #12

Open
elclanrs opened this issue Mar 8, 2014 · 4 comments
Open

Extremely slow curry #12

elclanrs opened this issue Mar 8, 2014 · 4 comments

Comments

@elclanrs
Copy link

elclanrs commented Mar 8, 2014

Bilby's curry compared to LiveScript's curry on same code. Image speaks more than words:
Imgur

@SimonRichardson
Copy link
Collaborator

Any chance of knowing what you're testing (examples, test cases), so we're not comparing apples and oranges.

@elclanrs
Copy link
Author

elclanrs commented Mar 8, 2014

I'm testing with some simple lazy streams code. I made a jsPerf. Bilby is like 10 times slower.

@kmarekspartz
Copy link

While performance is important, they are for totally different things.

Kyle Marek-Spartz

On March 8, 2014 at 3:42:47 AM, elclanrs (notifications@github.com) wrote:

Bilby's curry compared to LiveScript's curry.
Image speaks more than words:
Imgur


Reply to this email directly or view it on GitHub:
#12

@elclanrs
Copy link
Author

elclanrs commented Mar 8, 2014

I see the difference, but I think that bind is trying to do too much, so curry becomes slow. Bilby uses curry in many places, this optimization would improve performance a lot. Why not create a partial function, and a bind function?

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

No branches or pull requests

3 participants