chore(refactor): Remove optional global_id from methods that can get it from the definition #6283
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.
Description
Problem*
Followup to #6282
Summary*
Some methods in the
Elaborator
received aglobal_id: Option<GlobalId>
and adefinition: DefinitionKind
parameter. We found thatElaborator::elaborate_let
actually createddefinition
to carry the same global ID as it was given, soglobal_id: Some(id)
anddefinition: DefinitionKind::Global(id)
always carried the same value. We added an assertion that checked that they are never different.The next logical step is to remove the possibility of confusion by only carrying the ID in the definition.
Additional Context
Documentation*
Check one:
PR Checklist*
cargo fmt
on default settings.