I would add: **in any software, try to give precise and detailed error message
to the user of the cause of the problem**
Since a few hours, my tests don't compile any more and the message I have is
Error: type expected, but got: bool. I've tried changing the tests set,
expanded manually the macros on a reduced set, etc. It's working with other
tests but not this one. I know exactly the line where the problem occurs, but I
can't relate it to the error message. And because that's a compilation problem,
I can't call expandMacros to help the debugging...
With compiler maximum verbosity, it seems there's a bit of context:
Error: type expected, but got: bool
result = quote do:
^
Run
That's raging...
To solve problems, better give more details than less.
