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:
> How are the error messages?
langcc produces "confusing input pairs" 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.
> Does it produce source spans for intermediate AST nodes?
> Can it handle operator precedence without encoding the precedence into the grammar?
Yes - detailed in the documentation.
> Can it handle source-code-defined operator precedence?
Depends on what you mean by source-code-defined. The operations supported by langcc's precedence stanzas (detailed in the documentation) are quite comprehensive, and suffice to encode the operator precedence rules in Golang 1.17.8, for example.
Thanks! In general, I would avoid putting the documentation for a programming tool in a pdf hosted on Arxiv. It didn’t even occur to me that either of those links would be useful documentation. Additionally, pdf form isn’t the most helpful way to present documentation either.
> How are the error messages?
langcc produces "confusing input pairs" 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.
> 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....
> Can it handle operator precedence without encoding the precedence into the grammar?
Yes - detailed in the documentation.
> Can it handle source-code-defined operator precedence?
Depends on what you mean by source-code-defined. The operations supported by langcc's precedence stanzas (detailed in the documentation) are quite comprehensive, and suffice to encode the operator precedence rules in Golang 1.17.8, for example.