Open eclipse-viatra-bot opened 5 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:\
By Zoltan Ujhelyi on Jan 25, 2017 08:07
Postponed.
By Zoltan Ujhelyi on Oct 04, 2017 05:04
Postponing.
By Zoltan Ujhelyi on Feb 08, 2018 07:21
Postponing to a future release.
By Zoltan Ujhelyi on May 27, 2019 07:49
Bugzilla cleanup.
By Zoltan Ujhelyi on Nov 20, 2019 05:51
Postponing issues to the next release.
By Zoltan Ujhelyi on May 18, 2020 13:04
Postponing issues that will not be solved for version 2.5.
By Zoltan Ujhelyi on Nov 23, 2020 08:30
Mass postponing of issues to the 2.6 timeframe.
| --- | --- | | 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: