[EXPERIMENT DO NOT MERGE] remove span tracking during lowering #149918
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.
r? @ghost
Just a little experiment to see how much it gains us. All incremental tests pass, I've not found a place yet where it matters that we track them. It makes some sense, spans are relative to their parent anyway so it makes some sense that they're regenerated anyway if their parent changes. But I can't yet prove this. I am wondering how much perf it gains us.