Re-factor the isLittleEndian
/isEvalSupported
caching
#14751
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.
Re-factor the
isLittleEndian
/isEvalSupported
cachingThis functionality is very old, hence we should be able to improve the caching a little bit with modern JavaScript features.
Slightly simplify the
Catalog._readMarkInfo
methodWe don't need to first check if the Dictionary contains the key, since trying to get a non-existent key simply returns
undefined
and we're already ensuring that the value is a boolean.Furthermore, we shouldn't need to worry about the
Object.prototype
containing enumerable properties since the checks (insrc/core/worker.js
) done forArray.prototype
indirectly also coverObject
s. (Keep in mind that anArray
is just a special kind ofObject
in JavaScript.)