-
Notifications
You must be signed in to change notification settings - Fork 0
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
Compute hashes correctly when constructing internalised collections #568
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
e5189fa
Do not reset the fields of attributes unnecessarily
geo2a 1a02253
Build correct non-opaque key-values in `KMap` smart constructor
geo2a 241d0d2
Use updated elements in `KSet` and `KList` when hashing
geo2a 74991fb
Use strict left folds in internal collection smart constructors
geo2a da2f336
Sort and de-dupe non-opaque elements when building `KSet` and `KMap`
geo2a 7267da4
Factor-out sorting and de-duping into a function
geo2a f58e884
Add unit-tests for `pattern KSet`
geo2a e2e25cd
Add unit tests for `pattern KMap`
geo2a 436763a
Add LLVM integration test for plain ints
geo2a d072c5c
Add a failing LLVM set property test
geo2a 35b3a7e
Fix internalised definition in LLVM integration test
geo2a 74db142
Correct `setProp`, remove redundant function
geo2a 9f5ed34
Do not sort and de-dupe the nested `KMap`/`KSet`, only the result
geo2a File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.
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.
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.
The way this is failing in CI indicates that the smart constructor for
SymbolApplication
is not generating the expectedKSet
(bothres
and thesetAsConcat
result are notKSet
s).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.
Thanks for the thorough investigation @jberthold. I have to admit I though the test would ensure that the LLVM backend does not change the ordering of concrete sets (or would detect if it did), but upon introducing the changes, we are already comparing two internalised sets, which now de-duplicate and sort themselves, so I'm not sure if this test is helpful in the end.