Community
Participate
Working Groups
This planning bug aggregates many issues related to the objective tracing goal: Everything whose change requires incremental re-evaluation must be in the persisted trace.
Bug 515327 eventually resulted in a trace hierarchy for overrides/non-top relations. top overrides have a leaf TC_ class per override. Each TC_xxx class overrides a corresponding TI_yyy interface whose inheritance hierarchy replicates the overrides hierarchy. root variables (and status) are traced by the root interface. non-root variables are traced in the leaf class. non-top invocations have a WC_xxx class for each caller and a WI_xxx interface for each callee. Each WC_xxx class overrides a corresponding WI_yyy interface whose inheritance hierarchy replicates the overrides hierarchy for those clases that are directly invoked. The WI_xxx interface has the root variables (and status).
Bug 463969 deals with the need for accurate opposite modeling from the trace to ensure to-one properties give single headed mappings.
Bug 522344 deals with the need for sub-traces to trace each of a multiplicity of iterations.
Bug 522345 deals with the need for traces of operations that have NavigationCallExps accessing external model context.
Bug 522346 deals with regeneration of trace classes to suit what is actually appropriate post partitioning/merging and possibly trimming for non-incremental use.
Bug 522178 deals with the need for trace properties for intermediate terms in non-TemplateExp aspects of relation patterns.