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

performance-tuning === vs _Utils_eq #50

Open
decioferreira opened this issue Dec 9, 2024 · 0 comments
Open

performance-tuning === vs _Utils_eq #50

decioferreira opened this issue Dec 9, 2024 · 0 comments
Milestone

Comments

@decioferreira
Copy link

A suggestion by @miniBill that we should consider:

one suggestion from performance-tuning some elm code recently: double check that if you're doing x == 'c' that the compiler generates === and not _Utils_eq. I was able to make elm-xml-parser something like 3x faster on a real RSS feed

This should both be considered in context to the compiler code, as well as for considering improvements on the generated guida compiler code.

@decioferreira decioferreira added this to the v1.x milestone Dec 9, 2024
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

1 participant