Directly interfere to start kern sooner #562
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.
Simplified version of #466. Impact is most readily visible in the timing output:
Before:
kern may start as far right as the edge of the blue (be glyph) jobs.
After:
kern will consistently start at the left edge (earlier) of the blue jobs. Trying to detect a measurable performance boost with hyperfine was inconclusive, which is better flips run to run. Amusingly Oswald is now too fast for hyperfine to get useful #s at all on Mac. I tried the following: