eclipse-viatra-bot
commented
8 months ago By Gabor Bergmann on Dec 02, 2016 09:09
I see a number of ways how the PSystem-level type inference should be improved for v1.6:\
- Move type analysis services to a dedicated class (such as QueryAnalyzer), for separation of concerns (currently TypeHelper etc. offer useful but insufficient helpers)
- Make sure that types implied by called patterns can also be taken into account (even in case of recursion)
- Make sure the types of expressions (constants, evaluations and aggregations) are available for the inference (currently available only on the vql level, not in the PSystem)
- Introduce "double dispatch" type rules (multi-literal Horn clauses), e.g. type judgement x and y together imply Z. This would be a great performance saver for the dangling cross-references solution, where myEdge(x,y) AND in_scope(y) imply myTargetClass(y).
| --- | --- | | Bugzilla Link | 508592 | | Status | NEW | | Importance | P3 enhancement | | Reported | Dec 02, 2016 05:32 EDT | | Modified | Nov 23, 2020 08:30 EDT | | Version | 1.5.0 | | Reporter | Zoltan Ujhelyi |
Description
As discussed in https://git.eclipse.org/r/86114, the detailed type inferrer results are not available during runtime, only parameter types are reused at the generation of the pattern match and matcher classes. However, such type information would be beneficial for
We should think about how/where to make it available for the planners this information. The ideas we had were the following: