Fix TypeMerging bug with indirectly reachable public types #7031
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.
TypeMerging works by representing the type definition graph as a partitioned DFA
and then refining the partitions to find mergeable types. #7023 was due to a bug
where the DFA included edges from public types to their children, but did not
necessarily include corresponding states for those children.
One way to fix the bug would have been to traverse the type graph, finding all
reachable public types and creating DFA states for them, but that might be
expensive in cases where there are large graphs of public types.
Instead, fix the problem by removing the edges from public types to their
children entirely. Types reachable from public types are also public and
therefore are not eligible to be merged, so these edges were never necessary for
correctness.
Fixes #7023.