You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We all know that FEE's implementation in fontFeatures is very slow.
Does @simoncozens think that feaparser.rlib should also do any FEE-like input transformations? Should it allow people to add Rust callbacks to the parser for arbitrary tag names not in the FEA standard?
Or is fontFeatures, although slow, good enough? Should we instead focus on porting the slow parts of Python fontFeatures to Rust?
The text was updated successfully, but these errors were encountered:
We all know that FEE's implementation in fontFeatures is very slow.
Does @simoncozens think that feaparser.rlib should also do any FEE-like input transformations? Should it allow people to add Rust callbacks to the parser for arbitrary tag names not in the FEA standard?
Or is fontFeatures, although slow, good enough? Should we instead focus on porting the slow parts of Python fontFeatures to Rust?
The text was updated successfully, but these errors were encountered: