Closed coevolutions closed 1 week ago
This would expose ttf-parser api publicly which is something I deliberately avoid here for semver stability.
I see - I would like to avoid having to reparse the Face though if I already have it. Would you be okay with hiding it behind a feature flag?
Features also impact semver, i know of no correct way to workaround that.
Shielding this crate from upstream semver breaks prohibits use of upstream anywhere in the public api. Perhaps this is something we could revisit if ttf-parser stabilised e.g. on a v1.0.0. But currently upstream makes breaking changes routinely.
This allows FontRefs to be already created from pre-parsed faces. This can be useful to avoid having to reparse a face if we already have one, e.g. if we want to do shaping with rustybuzz, we should already have a parsed face and parsing it a second time is wasteful.