Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Produce UTS from `#lang resyntax/test`

Aperta
#586 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Ambito
tooling

Direzione di ricerca

La issue non indica file né test; inizia individuando il reader #lang resyntax/test e la sua implementazione di read-syntax. Confronta il suo output con i requisiti UTS elencati e con i requisiti UTS dell’original-reader, quindi risolvi le domande aperte indicate prima di considerare completo il reader.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

testing

The language's read-syntax implementation should produce Universal Tagged Syntax (UTS), which is my term for the kind of syntax objects I'm using to make Resyntax work on non-s-expression #langs. This implies a few restrictions:

  • The result of syntax-e anyways produces either an atom (a value with no syntax objects inside it) or a compound, which is a proper list of proper syntax objects.
  • Every list syntax object's first child is a shape tag, which is a keyword used to label the type of the surface syntax node.
  • Every atom has a 'uts-content syntax property whose value is a string. This is used as the textual form of the atom when writing the syntax object as text.
  • Every shape tag has a 'uts-separators syntax property whose value is a list of strings. The list should be equal to one plus the number of non-tag children in the tagged syntax object. This is combined with the textual forms of the child syntax objects when writing the tagged syntax object as text. The first separator is the prefix before the first child, the last separator is the suffix after the last child, and the middle separators are inserted between the children. The shape tags themselves are not written.

The one exception to the above is that the outermost syntax object returned by a #lang's reader is allowed to start with (module ...), with no shape tag. This is required for compatibility with Racket's #lang mechanism.

In addition to the above, a #lang's reader should produce original reader UTS, which is UTS where every syntax object is syntax-original? and where all syntax object source locations adhere to these rules:

  • Source locations never partially overlap.
  • One source location encloses another only when the first location's syntax object contains the second location's syntax object as a descendant.
  • One source location starting before another implies its syntax object comes before the other one's during a preorder traversal of the entire source file's syntax object.
  • Every syntax object's syntax-source value is the same and is in some way related to the original file or string containing the #lang directive.
  • Shape tags start at the same position as their parent syntax object and have a span of zero
  • Atoms have a uts-content string equal to the text at their source location in the original source code. Similarly, compounds have a uts-separators list whose strings are the substrings between its children, between the compound's start position and its first child's start, and between the compound's end position and its last child's end.
  • The syntax-span of a compound is equal to the spans of its children plus the total number of characters in the compound's uts-separators list.

Open questions include specifying how the #lang text should be reflected in the UTS properties, how autoformatting should work, how to detect comments, how indentation works, and probably lots of other stuff.

Lingua principale
Racket
Stelle
70
Fork
11
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di jackfirth/resyntax

Tutte le issue di jackfirth/resyntax

Issue simili

Altre issue su DevTools

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.