Short description
Show scope extensions in tooltips on user-defined constraints and references to those. For rules, only scope extensions of that rule should be shown.
Problem description.
When a specification has circular dependencies on declaration and query constraints, these end up as "unsolved" errors. These problems are notoriously hard to debug. Additional information on the scope extensions of rules/constraints can make debugging these easier.
Describe the solution you'd like
Consider the following specification:
Now, the tooltips should show the following for each predicate (reference) at the numbered positions:
"extends: 1 with 'var'"
"extends: s with 'var'"
"extends: 1 with 'var', 'mod'"
"extends: s with 'var'"
"extends: s with 'var'"
"extends: s with 'mod'"
"extends: s_mod with 'mod', 'var"
Describe alternatives you've considered
A first alternative would be to explain people how to inspect the scope extensions term in a compiled specification, but that is both too complicated for many users, and too repetitive.
Additional context
Scope extension properties are stored in the nabl2 custom analysis value, and can be retrieved from there.
Open question: How to access extension analysis for individual rules.
Short description Show scope extensions in tooltips on user-defined constraints and references to those. For rules, only scope extensions of that rule should be shown.
Problem description. When a specification has circular dependencies on declaration and query constraints, these end up as
"unsolved"
errors. These problems are notoriously hard to debug. Additional information on the scope extensions of rules/constraints can make debugging these easier.Describe the solution you'd like Consider the following specification:
Now, the tooltips should show the following for each predicate (reference) at the numbered positions:
Describe alternatives you've considered
A first alternative would be to explain people how to inspect the scope extensions term in a compiled specification, but that is both too complicated for many users, and too repetitive.
Additional context
Scope extension properties are stored in the nabl2 custom analysis value, and can be retrieved from there. Open question: How to access extension analysis for individual rules.