Slightly simplify the XRef cache lookup in XRef.fetch
#11373
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.
Note that the XRef cache will only hold objects returned through
Parser.getObj
, and indirectly viaLexer.getObj
. Since neither of those methods will ever returnundefined
, we can simplyassert
that when inserting objects into the cache and thus get rid of one function call when doing cache lookups.Obviously this won't have a huge effect on performance, however
XRef.fetch
is usually called a lot in larger documents and this patch thus cannot hurt.