Stanisław Barzowski

Yeah, having `null == id` in this context seems to be quite convenient. This feature is not strictly required for this flow. You can have: ``` local id(x) = x;...

And there has been no progress. If someone wants to pick it up, it would be a very welcome addition. I'll be happy to help in case of any questions.

> limitation, as I'm probably not sure, why this limitation is needed. To avoid ambiguity when nesting. How do you know if `f(g(_))` is a partial application of `g` or...

> I think the proposed semantics is quite vague, I do not like that both value |> mapper and value |> mapper(_) can be used, why not choose one of...

Thanks, adding more standard hash functions is a good thing. Unfortunately, going from 0 external dependencies to one (two with absl) is a pretty inconvenient. We need to support the...

If we will go forward with parseYaml we will probably want to add shared library dependencies anyway, so adding openSSL should't change that much.

Being able to specify shape in classDef would be really helpful – it would allow specifying semantic classes of nodes and styling them separately. This would be very useful when...

IMO words would be a little bit more readable in this context.

Hmmm... how is `style` different from `classDef` in this aspect? IIUC both are currently using CSS attributes directly to style a node (`style` is used inline and `classDef` is used...

I think it's a good idea and the code looks reasonable. What is missing?