Glyph serialization: Error out if any floats are infinite, subnormal, or NaN
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 61
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Norad will currently write out floats like `NaN`. I am not sure this is a good idea? The [spec](https://unifiedfontobject.org/versions/ufo3/conventions/#float) does not mention it but the definition seems to imply that we don't want float corner cases. ot sure we should error out or instead make their construction impossible with newtypes or something?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Norad's glyph serialization entry points and reproduce how NaN, infinite, and subnormal floats are written. Decide whether serialization should reject these values or prevent their construction, then add coverage for the chosen behavior and verify the resulting UFO output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100