Example error report for an unknown predicate/literal (in the IR), although we should probably detect that it's an operator and report a different message:
Adds position and a new type SpannedPosition which is similar to the pair approach and doesn't contain a reference to the corresponding string slice, to avoid lifetime and Rc issues.
[x] Compiler error fixes
[x] Format string correct position - note that this is currently done by associating the positions with the generated literals not the new terms.
[x] Usage of the source span in error messages. E.g. using VerboseError I use codespan for the SLD error reporting.
[x] Add length of the span
[x] Think about whether to use pair or LocatedSpan in the type.
Related to #40.
Example error report for an unknown predicate/literal (in the IR), although we should probably detect that it's an operator and report a different message:
Adds
positionand a new typeSpannedPositionwhich is similar to the pair approach and doesn't contain a reference to the corresponding string slice, to avoid lifetime and Rc issues.usingI useVerboseErrorcodespanfor the SLD error reporting.Related to #32.