-
Notifications
You must be signed in to change notification settings - Fork 125
Implement this, operator, and parameter resolution on Containers #2673
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
Implement this, operator, and parameter resolution on Containers #2673
Conversation
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. Great tests. Simple Trie.
|
||
class StringTrie { | ||
final Map<int, StringTrie> children = {}; | ||
bool valid = false; |
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.
Would you mind documenting this field? I think I know what it means, but maybe not in the context of a field on a whole trie.
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.
done
As the title says. We can't directly use Scope and analyzer resolution here without some more digging into the analyzer, but we can bring the current implementation up to speed.
Link resolution equivalence moves from 98% => 99% on the SDK, 72% => 73% on Flutter. While the link resolution equivalence delta is small, the link resolution equivalence doesn't account for parameters not being found at all. That would have led to many false positives.