Skip to content
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

Stop searching for setup when first match found #1004

Merged
merged 2 commits into from
Apr 21, 2020

Conversation

stakx
Copy link
Contributor

@stakx stakx commented Apr 21, 2020

This would have caused a regression before version 4.13, but appears to work now—and should result in improved performance due to the reduced amount of matching performed.

Searching for a more perfect match after a matching setup has been
identified appears to go against the principle of more recent setups
overriding earlier ones, anyway.
The test changed here shouldn't have passed in the first place, since
the setup for `Method<object>` essentially shadowed the earlier ones
for `Method<bool>` and `Method<int>`.
@stakx stakx added this to the 4.14.0 milestone Apr 21, 2020
@stakx stakx merged commit 4586f77 into devlooped:master Apr 21, 2020
@stakx stakx deleted the setup-matching-simplification branch April 21, 2020 05:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant