The goal is to replace ttf-parser with small diffs that don't break tests. With that in mind, I'm using the following process:
Replaces calls into ttf-parser with stubs that contain the simplest equivalent read-fonts code that preserves behavior. This code may not be architecturally ideal, might have performance issues and will probably be missing comments and tests.
Audit the new code, likely moving the bulk of it to read-fonts. Make it commented, tested and fast.
Implement architectural changes to match the patterns used in skrifa. Most specifically, let's support acceleration structures that aren't bound to the lifetime of font data.
The rationale for this approach is that it’ll be vastly simpler to do cleanup and architectural changes if we’re not dancing around ttf-parser (or worse, mixed ttf-parser/read-fonts) code.
The goal is to replace ttf-parser with small diffs that don't break tests. With that in mind, I'm using the following process:
The rationale for this approach is that it’ll be vastly simpler to do cleanup and architectural changes if we’re not dancing around ttf-parser (or worse, mixed ttf-parser/read-fonts) code.
ref comments in #8