Re-factor the charsCache
on Font
-instances
#13443
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.
Currently
charsCache
is initialized lazily, which considering that it just contains a simpleObject
doesn't seem entirely necessary. This first of all forces us to do repeated exists-checks in theFont.charsToGlyphs
method, and secondly the similar/relatedglyphCache
is already initialized eagerly.Furthermore, this patch also does a bit of clean-up in the
Font.charsToGlyphs
method since this code is quite old.