Not informative error messages about ructe HOT 3 CLOSED

Agreed. The first one would be easy enough to fix by failing the build job when there is an error in compiling a template. That would mean only seeing errors like the second kind, and never attempt to actually compile the rust code that uses the templates when template compilation fails.

To improve the second kind require learning to provide specific parser error messages from the nom parser generator. I'm not even sure how good support nom has for that yet, but I will look into it.

from ructe.

I've been experimenting some more with this (without committing any code). It seems to be possible to get rather good error information from nom, but the parser has to be partially reconstructed; I have typically created largish sub-parsers (e.g. one parser for a complete @for item in items { something } and one for @if condition { something }) and joined them with alt!. This won't work since the generated parser will ignore errors in all but the last branch. It can be fixed by using the switch! macro rather than alt!. But I still have problem with looping constructs, which will just assume the loop ended on any error, rather than reporting the actual error.

I have not given up, but this may take some time.

from ructe.

I think this is done for now (although not released yet).

from ructe.