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, if a virtual doc is undefined, that information is not cached during evaluation (whereas if it is defined, the value is cached.) To avoid recomputing the virtual doc and arriving at undefined, evaluation should cache the fact that the doc was undefined.
The text was updated successfully, but these errors were encountered:
With this change, `undefined` outcomes of complete rule evaluations
are now also cached. Previously, only defined results had been cached,
and empty partial sets/objects.
In the case of partial rules with string keys, the introduction of ref heads
changed how they had been evaluated: Before, they had been evaluated
as partial sets, and thus got cached when empty. After, they had been
evaluated as complete rules (with ref heads), and if they were undefined,
they had _not_ been cached. This caused a performance regression.
Fixes#593.
Signed-off-by: Edward Paget <edward.paget@chime.com>
Currently, if a virtual doc is undefined, that information is not cached during evaluation (whereas if it is defined, the value is cached.) To avoid recomputing the virtual doc and arriving at undefined, evaluation should cache the fact that the doc was undefined.
The text was updated successfully, but these errors were encountered: