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
We see that the IEnumerable arguments is stored in Arguments. Whenever a visitor passes over this node and uses Argument multiple times, IEnumerable is evaluated over and over again, possibily triggering expensive re-visiting of the expression passed into the argument.
We should change Arguments to an array, and call ToArray() once in the constructor.
The text was updated successfully, but these errors were encountered:
Can you include me on the PR review? As wanting to check what this to array is in.
For things like large codesystems or lists it can be super expensive if not required...
If you look at this code from ExpressionNode.cs in the fhirpath engine:
We see that the IEnumerable arguments is stored in Arguments. Whenever a visitor passes over this node and uses Argument multiple times, IEnumerable is evaluated over and over again, possibily triggering expensive re-visiting of the expression passed into the argument.
We should change Arguments to an array, and call ToArray() once in the constructor.
The text was updated successfully, but these errors were encountered: