File detail
syntax-edge-cases.rq
reqlan rq/language/syntax-edge-cases.rq
| Idea | Status | Tags | Summary |
|---|---|---|---|
| nested_curly_braces | if there is a prose block containing curly braces, { such as this one } they should be treated as part of the prose. Matching braces that end a line — including adjacent pairs like { { SITE_URL } } — stay in the body; they must not close the enclosing idea. A lone `}` on its own line still closes the structural block so an unbalanced prose `{` cannot swallow the idea closer. | ||
| context_sensitive_lexer_scaling | done | Context-sensitive token classification for structural / prose braces and top-level import keywords must remain linear in document size. The lexer records brace-depth changes sparsely ( not per-character tables ) and looks them up in log time while tokenising, so workspace language-server initialization and editor re-lexes stay bounded. Code fences are skipped during the brace scan so example braces cannot inflate work or desync depth. Bounded work still assumes the lexer / parser * returns *; unbounded hangs are cut by ["./parser_lexer.rq".parse_budget_timeout]. | |
| one_liner_curly_brace_context | this should { be acceptable } as well | ||
| closing_nested_curly_braces | if, for some reason, there is a prose block containing only closing curly braces, they should be escaped and allowed \ } like this. |
Initialising graph…