I write a considerable amount of markdown these days, but I've developed a numbering style that is deliberately not part of the syntax.
(1) Foo.
Bar.
(2) Baz.
Auto (re-)numbering can be really surprising, and numbered sections tend to be narrower and harder to read.
miniblog.
Related Posts
I've had a surprising amount of success asking an LLM to try projects in my toy programming language and report language or tooling issues.
Today it noticed that foo(bar,) is syntactically legal but assert(bar,) is not. The parser error is poor in this case too. A real UX bug!
Language design question: what type should `while True {}` have?
Bottom: It doesn't contain any `break` statements.
Unit: Treat loops with/without `break` consistently.
I already have lints that warn on unreachable code after diverging loops, so the Unit case feels surprising.
@krinkle A surprising number of PL design workarounds are "just add another equals sign" 🙃