-
-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
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
System.InvalidProgramException : The JIT compiler encountered invalid IL code or an internal limitation. #419
Comments
@michaelgrosner Could you provide the missing Obj and Nested types so that I can compile and test this expression? |
Sure, here's something that reproduces the issue:
I was also able to reproduce it this way, too:
|
@michaelgrosner Thank you for the refined test, adding to the queue to fix. |
dadhi
added a commit
that referenced
this issue
Oct 13, 2024
dadhi
added a commit
that referenced
this issue
Oct 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I've been trying out FastExpressionCompiler in order to replace my usages of Expression.Compile. I am running into a situation that I can't figure out why FEC breaks while Expression.Compile handles the expression.
In pseudo-code, I am trying to get a RefFunc<T, bool> which is "Obj.X > 2 * Obj?.Nested?.Y". "X" and "Y" are both nullable doubles, and "Obj" and "Nested" are classes with other fields.
This is what ToExpressionString returns for me:
I think it's probably due to the nested null checks in "Obj?.Nested?.Y". But the standard Expression.Compile handles this just fine. Do you have any insight into how to fix this, either in this library or in my code? I have seen this issue when running on 4.2.1 and 4.0.0 on .NET 6.
The text was updated successfully, but these errors were encountered: