Yann Hamdaoui

> I guess another option would be a "gas"-powered evaluation, like the way equality is tested in the typechecker. I think that might not prove easy, at least not without...

> I think matklad's solution doesn't work if the worker is doing a long-running computation, right? It relies on having a cooperative cancellation point (i.e. the point where the worker...

We don't generate markdown by hand, but we build an AST and use a crate called `comrak`, and specifically use the `format_commonmark` function. It seems that a backslash followed by...

I didn't file an issue on comrak because we weren't using the latest version, but I really think this is a bug on their end. The commonmark standard says clearly...

Incidentally, I think updating to latest `comark` is valuable even if it doesn't solve the current problem, so feel free to push those changes @jneem :slightly_smiling_face:

On the other hand, I think it's in fact not possible to have a line break at the end of a code block in markdown. That is, the AST we're...

The thing is that I'm now convinced the root of the problem is around comrak rendering of lists. What we did was a hacky work-around, but we shouldn't have to...

Maybe that's the occasion to get rid of the vim plugin and advise people to use the tree-sitter grammar instead? That would be one less grammar to maintain.

I wonder what could be a working type annotation, though. Currently there's no obvious way of typing heterogeneous arrays (at least without the subtyping of RFC004): ```nickel nickel> ["hello ",...

I must admit that I'm a bit reluctant to the general idea of making metadata entirely dynamic. One of the point of documentation is to be used in part by...