mirror of
https://github.com/unisonweb/unison.git
synced 2024-09-11 10:35:57 +03:00
1dc181b99a
`cmark`’s pretty-printer matches our output pretty well, with a few differences: - it puts a space between the fence and the info string for in code blocks; - it prefers `-` over `*` for bulleted lists (as do I) and it indents them; - it `\`-escapes certain chars very conservatively; - it prefers indented/unfenced code blocks if there is no info string; and - it prefers `*` over `_` (unlike any sane person). This also shows how the change fixes a number of issues: - fix2158-1.output.md also illustrates how this change fixes #1809; - alias-many.output.md and input-parse-errors.output.md show how fenced code blocks without an info string would use the beginning of the content as the info string; - transcripts-round-trip/main.output.md shows how output blocks for generated `unison` stanzas (which could contain nested fenced blocks) might not have long-enough fences; and - error-messages.output.md and generic-parse-errors.output.md show how Unison errors were reported on the wrong line number (and thus the printed error lines were also incorrect).
687 B
687 B
Transcript parser hidden errors
When an error is encountered in a unison:hide block
then the transcript parser should print the stanza
and surface a helpful message.
g 3
🛑
The transcript failed due to an error in the stanza above. The error is:
This looks like the start of an expression here
1 | g 3
but at the file top-level, I expect one of the following:
- A binding, like g = 42 OR
g : Nat
g = 42
- A watch expression, like > g + 1
- An `ability` declaration, like unique ability Foo where ...
- A `type` declaration, like structural type Optional a = None | Some a