-
Notifications
You must be signed in to change notification settings - Fork 186
Use StrictTriple for splitMember #1172
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
Conversation
This tracks the strictness in the implementation more cleanly and makes it easier to optimize. For instance, with GHC 9.12.2, the Set intersection benchmark time improves by 13%.
treeowl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch.
|
I assume the triple itself gets unboxed regardless, and this just helps the analysis? |
|
Yes. Core beforeFor some reason, the returned set ( Core after |
|
That might be worth a GHC ticket, especially if the problem survives code generation. |
This tracks the strictness in the implementation more cleanly and makes it easier to optimize. For instance, with GHC 9.12.2, the Set intersection benchmark time improves by 13%.