Ligature requests: .< and >. and .~ and !.
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 82k
- Forks
- 3.2k
- PR merge metrics
- No merged PRs in 30d
Description
In MetaOCaml, .< e >. is used to encode the quasi-quoting of expression e, whereas .~e is to unquote / escape. These are beautifully encoded in the paper and documentation, but look horrific in actual source-code. Compare:
vs.
Typographic ligatures could go a long way towards improving the usability of MetaOCaml; I'd really love to see these supported by Fira Code. (=
(Also see #317 and, especially, #380.)
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 reviewing the MetaOCaml syntax described in the issue and the related discussions in #317 and #380. Inspect how Fira Code represents existing programming ligatures, then verify that .<, >., .~, and !. render as the requested ligatures without disrupting surrounding source text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100