You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently copy propagation is only applied to the queries returned by partial evaluation. If the partial evaluation result includes support modules, copy propagation is not applied to the bodies of rules in those modules. By default, we should apply copy propagation in all of the partial evaluation results. In cases where clients cannot consume support modules, the additional latency will not be important (since the presence of support modules will likely result in an error). In cases where clients CAN consume support modules, the removal of unnecessary variables will simplify processing for clients.
The text was updated successfully, but these errors were encountered:
Previously copy propagation was only being applied to queries returned
by partial eval. The assumption was that clients would typically be
implemented to deal with queries and that support rules would be
unhandled. In some cases though, clients may be capable of handling
support rules. For them, it's better if we apply copy propagation to
both queries and rule bodies.
Note, we ensure that rule bodies are non-empty so that comparisons to
parsed rules that are equivalent (but lacking a body) succeed.
Fixesopen-policy-agent#911
Signed-off-by: Torin Sandall <torinsandall@gmail.com>
Previously copy propagation was only being applied to queries returned
by partial eval. The assumption was that clients would typically be
implemented to deal with queries and that support rules would be
unhandled. In some cases though, clients may be capable of handling
support rules. For them, it's better if we apply copy propagation to
both queries and rule bodies.
Note, we ensure that rule bodies are non-empty so that comparisons to
parsed rules that are equivalent (but lacking a body) succeed.
Fixes#911
Signed-off-by: Torin Sandall <torinsandall@gmail.com>
Currently copy propagation is only applied to the queries returned by partial evaluation. If the partial evaluation result includes support modules, copy propagation is not applied to the bodies of rules in those modules. By default, we should apply copy propagation in all of the partial evaluation results. In cases where clients cannot consume support modules, the additional latency will not be important (since the presence of support modules will likely result in an error). In cases where clients CAN consume support modules, the removal of unnecessary variables will simplify processing for clients.
The text was updated successfully, but these errors were encountered: