Bdd negation and difference optimizations#15287
Merged
josevalim merged 7 commits intoApr 17, 2026
Merged
Conversation
josevalim
reviewed
Apr 17, 2026
josevalim
reviewed
Apr 17, 2026
josevalim
reviewed
Apr 17, 2026
Co-authored-by: José Valim <jose.valim@gmail.com>
Member
|
💚 💙 💜 💛 ❤️ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Those slow downs happen when using
bdd_intersection / bdd_differenceovertuple_intersection / tuple_difference:Found what was causing the formatter.ex slowdown when not using bdd_intersection: it was a blow-up in bdd_negation. Added a new formula for it.
Found out what was causing the slowdown for macro.ex 4s tc times: some blowup in bdd_diff related to negation.
Also fixed a bug on tuple_insert_at.