https://hackerpaper.kaipfister.de/p/2209.08385/Collected HN comments and submissions linking this paper.enMon, 02 Nov 2026 11:16:22 GMThttps://news.ycombinator.com/item?id=32964078urn:hackerpapers:mention:2209.08385:32964078Sat, 24 Sep 2022 16:18:52 GMT<p>Readers who are interested in parsing theory may also enjoy the companion technical report: https://arxiv.org/pdf/2209.08383.pdf as well as a brief users&#x27; manual, available here: https://arxiv.org/pdf/2209.08385.pdf</p><p><a href="https://hackerpaper.kaipfister.de/p/2209.08385/">Paper and discussion history</a>. A mention is not an endorsement.</p>cs.PLhttps://news.ycombinator.com/item?id=32961553urn:hackerpapers:mention:2209.08385:32961553Sat, 24 Sep 2022 11:32:20 GMT<p>The README is a work in progress, but some of these answers can be found in the documentation (https://arxiv.org/abs/2209.08385). In particular: &gt; How are the error messages? langcc produces &quot;confusing input pairs&quot; for LR conflicts, which enable the user to pinpoint the cause of the error much more easily than the opaque shift/reduce errors in tools such as yacc/bison. &gt; Does it produce source spans for intermediate AST nodes? Yes! You can find an example in https://github.com/jzimmerman/langcc/blob/main/examples/calc.... &gt; Can it handle operator precedence without encoding the precedence…</p><p><a href="https://hackerpaper.kaipfister.de/p/2209.08385/">Paper and discussion history</a>. A mention is not an endorsement.</p>cs.PL