Better support for Typst `auto`
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 76
- Forks
- 11
- Avg merge
- 9h 5m
- Merged PRs (30d)
- 1
Description
Currently we do have VAuto defined, but it works quite different from what Typst works.
In Typst, auto values are realized when it's actual rendered. For example, if I do #stroke().paint, I will see auto instead of an actual color.
To have support for more Typst functionalities (such as #76), refining the way that VAuto works would be important.
Specifically, these are desirable:
- Functions can take
VAutoas argument. VAutoare actually stored asVAutoin constructs, not as a concrete default value.VAutoare resolved to a concrete value later, whether when it's being converted to Pandoc AST, repr string, or an element.
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 by tracing VAuto through function arguments, stored constructs, and the conversion paths to Pandoc AST, repr strings, and elements. Compare the current behavior with the listed Typst examples and establish tests showing that VAuto is preserved until each late-resolution boundary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100