reverofevil

Markdown with shorter lines might be as hard to edit and merge. - Somebody edited a line, and now it's longer or shorter than others. Should it be kept as...

Something [like this](https://github.com/shurcooL/markdownfmt).

(Links from there for whoever wants to make an article on polynomial mincost flow: [article in Chinese](https://ouuan.github.io/post/%E5%9F%BA%E4%BA%8E-capacity-scaling-%E7%9A%84%E5%BC%B1%E5%A4%9A%E9%A1%B9%E5%BC%8F%E5%A4%8D%E6%9D%82%E5%BA%A6%E6%9C%80%E5%B0%8F%E8%B4%B9%E7%94%A8%E6%B5%81%E7%AE%97%E6%B3%95/ ), [lectures with algorithm description](https://web.stanford.edu/class/cs361b/files/cs361b-notes.pdf), [implementation](https://github.com/Laakeri/tiralabra/blob/master/src/scalingcirculation.cpp))

Quite sure there was a problem on UV judge about superman flying around columns, but, of course, it's down.

Coauthor here, go for it! (@Chillee And if you don't mind, how on Earth did you find our guide?)

I've just made a [rough and ready translation](https://gist.github.com/polkovnikov-ph/ba01c0bc543dec7cac9473b0ca21024f), because, well, who else is a Russian speaker here. I'm unsure if I should make a PR out of it, because that's...

I don't think it should be published as is, but if everyone is fine with it, I'll rewrite it with proper grammar and make a PR.

I'm just a bit busy at the moment. Will come back to this in a week.

Sorry, I just found this issue from the link of the mentioned issue. A bit bitter truth is 1. Formal AST specification is only useable for code generation if semantics...

> make assumptions about the ESTree spec that aren't things that have been goals of this project I didn't go far to look up that it aims to be >...