Skip to content

Fix StringTrie so it handles partial matches better #2813

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

Merged
merged 1 commit into from
Sep 28, 2021

Conversation

jcollins-g
Copy link
Contributor

Fixes #2808. A silly bug where the StringTrie used for operator matching wasn't handling some boundary conditions very well. Fix and add tests.

@google-cla google-cla bot added the cla: yes Google CLA check succeeded. label Sep 27, 2021
@jcollins-g jcollins-g requested a review from srawlins September 28, 2021 00:04
@jcollins-g jcollins-g merged commit 04945d9 into dart-lang:master Sep 28, 2021
@jcollins-g jcollins-g deleted the fix-stringtrie branch September 28, 2021 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Google CLA check succeeded.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RangeError (end): Invalid value: Not in inclusive range 7..8: 1
2 participants