Fix re-processing cross-reference when node kind changes #17883
Merged
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.
This is quite a bad bug. Currently we rely on
SymbolNode
being updated in-place for all indirect references, but this is not the case when node kind (FuncDef
,Decorator
, etc.) changes, in this case a newSymbolNode
is created. I fix this by forcing reprocessing if the node kind changes.This currently blocks support for PEP 702, see #17476, so I will not wait for long before merging.
cc @JukkaL @hauntsaninja