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
The above code removes the currently processed element from interpolationTarget, just like a function call would do, but then places newly found elements to be processed into that collection.
This risks an infinite recursion loop if the analysed model contains cycles. So, it's possible that the function is fed a model with cycles in it.
The text was updated successfully, but these errors were encountered:
PR mojohaus#538 switch to non-deprecated ModelInterpolator changed that.
The old model interpolator implements recursion using its own stack (
interpolationTarget
):The above code removes the currently processed element from
interpolationTarget
, just like a function call would do, but then places newly found elements to be processed into that collection.This risks an infinite recursion loop if the analysed model contains cycles. So, it's possible that the function is fed a model with cycles in it.
The text was updated successfully, but these errors were encountered: