perf(core): Remove addNonEnumerableProperty
from packages/core/src/tracing/utils.ts
#15811
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.
Extracted from #15765
resolves #15810
addNonEnumerableProperty
is pretty expensive because ofObject.defineProperty
, so this changes usage of span utils (which are called frequently) to avoid usage ofaddNonEnumerableProperty
.addNonEnumerableProperty
is replaced with weak maps, which has the added benefit of being more GC friendly (addNonEnumerableProperty
causes hard references to be created between the objects).The only downside of switching to this approach is that we lose the
try catch
built intoaddNonEnumerableProperty
, but I think thats fine given the nature of the changed methods.