Experiment: fast compiling fontique #419
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Nico Burns <[email protected]>
Signed-off-by: Nico Burns <[email protected]>
Signed-off-by: Nico Burns <[email protected]>
nicoburns
force-pushed
the
fast-fontique
branch
from
879d932 to
0ce59bb
Compare
Signed-off-by: Nico Burns <[email protected]>
nicoburns
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
An experiment in making Fontique compile fast. Brings clean build time down to around 4 seconds.
Depends on:
Futher possible improvements:
icu_locale_coredepread-fontsto add an option to useunsafebytemuck impls rather thanbytemuck_deriveCharmapIndexoptional(failing CI because HarfRust version of
read-fontsdoesn't match version used by Parley/Fontique in this PR)Full build timings