-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Exclusivity] Switch static checking to use IndexTrie instead of Proj… #10305
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
[Exclusivity] Switch static checking to use IndexTrie instead of Proj… #10305
Conversation
…ectionPath IndexTrie is a more light-weight representation and it works well in this case. This requires recovering the represented sequence from an IndexTrieNode, so also add a getParent() method.
\cc @atrick |
@swift-ci Please smoke test and merge |
@swift-ci please test |
Build failed |
@swift-ci please test and merge |
👍 |
Huh. something is wonky with the PR test. Taking a look. |
@swift-ci please test and merge |
@swift-ci Please clean test |
1 similar comment
@swift-ci Please clean test |
Build failed |
Build failed |
Master is busticated. There's a PR going in in a few mins that should fix it, then I'll kick this off again. |
@swift-ci please test and merge |
@swift-ci please test |
Comment has to be before the trigger :) |
jinx! |
Build failed |
We had more breakage on master. Should be fixed now... Let's try this again. |
Build failed |
Let's "trie" this again. |
…ectionPath
IndexTrie is a more light-weight representation and it works well in this case.
This requires recovering the represented sequence from an IndexTrieNode, so
also add a getParent() method.