Logical OR, AND, and NOT variants
Open
Nobody has claimed this yet.
proposal
- Dominant language
- Rust
- Stars
- 53
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Context
This proposal is based on typst/typst#4939. See the pull request description and discussion thread for additional context and concerns.
Proposal
Add the symbol variants from the following table under sym.
| Character | Name |
|---|---|
| ⩞ LOGICAL AND WITH DOUBLE OVERBAR (Binary) | eq.and |
| ⩢ LOGICAL OR WITH DOUBLE OVERBAR (Binary) | eq.or |
| ⫬ DOUBLE STROKE NOT SIGN (Relation) | not.double |
| ⌐ REVERSED NOT SIGN (Normal) | not.rev |
| ⫭ REVERSED DOUBLE STROKE NOT SIGN (Relation) | not.rev.double |
| ⌙ TURNED NOT SIGN (Normal) | not.inv |
| ⩠ LOGICAL AND WITH DOUBLE UNDERBAR | and.eq |
| ⩙ LOGICAL OR OVERLAPPING LOGICAL AND (Relation) | and.or and or.and |
| ⩘ SLOPING LARGE AND (Binary) | and.sloped (maybe and.slope) |
| ⩚ LOGICAL AND WITH MIDDLE STEM (Binary) | and.stem |
| ⩜ LOGICAL AND WITH HORIZONTAL DASH (Binary) | and.struck |
| ⩕ TWO INTERSECTING LOGICAL AND (Binary) | and.twice |
| ⨇ TWO LOGICAL AND OPERATOR (Large) | and.twice.big |
| ⩣ LOGICAL OR WITH DOUBLE UNDERBAR (Binary) | or.eq |
| ⩗ SLOPING LARGE OR (Binary) | or.sloped (maybe or.slope) |
| ⩛ LOGICAL OR WITH MIDDLE STEM (Binary) | or.stem |
| ⩝ LOGICAL OR WITH HORIZONTAL DASH (Binary) | or.struck |
| ⩖ TWO INTERSECTING LOGICAL OR (Binary) | or.twice |
| ⨈ TWO LOGICAL OR OPERATOR (Large) | or.twice.big |
Contributor guide
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 locating the existing sym symbol definitions and their tests in the repository, then compare the current naming conventions with the proposal table. Add the listed logical OR, AND, and NOT variants, resolve the two naming alternatives, and verify that every requested symbol is exposed under its intended name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- content
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100