[ty] Avoid temporarily storing invalid multi-inference attempts#22103
Merged
[ty] Avoid temporarily storing invalid multi-inference attempts#22103
Conversation
Member
|
(Is this related to astral-sh/ty#2123 or totally different?) |
Diagnostic diff on typing conformance testsNo changes detected when running ty on typing conformance tests ✅ |
|
CodSpeed Performance ReportMerging #22103 will improve performance by 6.9%Comparing Summary
Benchmarks breakdown
Footnotes
|
Member
Author
|
I haven't looked at astral-sh/ty#2123, and locally this doesn't seem to help, so probably unrelated. |
a54c846 to
6c910ba
Compare
6c910ba to
c0a1a10
Compare
AlexWaygood
approved these changes
Dec 20, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
I missed this in #22062. This avoids exponential runtime in the following snippet:
Eventually I want to refactor our multi-inference infrastructure (which is currently very brittle) to handle this implicitly, but this is a temporary performance fix until that happens.