The new SPT implementation does not support error markers

test error on Boolean and Int [[ true && [[3]] ]] 1 error results in:

Multiple markers at this line
 - Type mismatch: eypected Boolean got Int in Logic Operation
 - No error/warning/note marker
 - Error/warning/note marker expected at selection(s)

Without exact error markers, test error on Boolean and Int [[ true && 3 ]] 1 error, the test works fine.

Submitted by Daco Harkes on 12 January 2016 at 10:23

On 12 January 2016 at 10:44 Gabriël Konat tagged error

On 12 January 2016 at 10:44 Gabriël Konat removed tag @gohla

On 12 January 2016 at 17:00 Daco Harkes commented:

The error log states: The analysis produced a message on region (2123,2123) which can not be resolved. in org.metaborg.meta.lang.spt.strategies.analyze_fragment_0_2 (Worker-46).


On 14 January 2016 at 17:12 Gabriël Konat commented:

This should be (mostly) solved by using the Spoofax Core tracing service.


On 14 January 2016 at 18:45 Daco Harkes commented:

Yes, I confirm that all errors except one are solved in my test set. (The one error that is left over has weird behavior anyway, as the error message shows up on a full AST node in the SPT test, but only on the first child in a language file.)

Thank you very much!

Issue can be closed.


On 15 January 2016 at 14:28 Daco Harkes commented:

The last test was indeed a bug in my language. This issue is completely resolved.


On 10 June 2016 at 15:57 Gabriël Konat closed this issue.

Log in to post comments