Remove unpack
field from SemanticIndexBuilder
#14101
Open
+50
−47
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
Related to #13979 (comment), this PR removes the
current_unpack
state field fromSemanticIndexBuilder
and passes theUnpack
ingredient via theCurrentAssignment
->DefinitionNodeRef
conversion to finally store it onDefintionNodeKind
.This involves updating the lifetime of
AnyParameterRef
(parameter todeclare_parameter
) to use the'db
lifetime. Currently, all AST nodes stored on various enums are marked with'a
lifetime but they're always utilized using the'db
lifetime.This also removes the dedicated
'a
lifetime parameter onadd_definition
which is currently being used inDefinitionNodeRef
. As mentioned, all AST nodes live through the'db
lifetime so we can remove the'a
lifetime parameter from that method and use the'db
lifetime instead.