We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This should succeed.
true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true && true
It's hitting protections for max nesting depth: Message:"Max call depth exceeded.
Note that arranging in flat form works:
And( true,true,true,true,true, true,true,true,true,true, true,true,true,true,true, true,true,true,true,true, true,true,true,true,true, true,true,true,true,true, true,true,true,true,true, true,true,true,true,true)
The text was updated successfully, but these errors were encountered:
Can't hosts simply
new PowerFxConfig(...) { MaxCallDepth = NEW_MAX_NUMBER }
Sorry, something went wrong.
The problem is that fundamentally, a && b && c shouldn't threaten a stack overflow.
a && b && c
This may help:
Power-Fx/src/libraries/Microsoft.PowerFx.Core/IR/IRTranslator.cs
Line 600 in 5132996
I think similar optimization may help for all the operator that we convert to call node.
anderson-joyle
No branches or pull requests
This should succeed.
It's hitting protections for max nesting depth: Message:"Max call depth exceeded.
Note that arranging in flat form works:
The text was updated successfully, but these errors were encountered: