Fix the order of BE kern gathering #678
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.
I believe this resolves the issue described at #647 (comment) by applying the same fix as #655 to the second scatter/gather we do on kerning.
I have filed #677 to track making this simpler as it's definitely harder than it shoudl be.
The following produces observably unstable output on main, usually in 2-4 builds, and is stable through 20 cycles after the fix:
JMM if happy.