-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Perplexing decompiled expression #135
Comments
magicmoux
pushed a commit
to magicmoux/DelegateDecompiler
that referenced
this issue
Jan 6, 2019
Force DecompilerTestBase to visit decompiled expressions
Closed
magicmoux
pushed a commit
to magicmoux/DelegateDecompiler
that referenced
this issue
Jun 18, 2019
hazzik
added a commit
that referenced
this issue
Aug 9, 2019
hazzik
added a commit
that referenced
this issue
Aug 9, 2019
hazzik
added a commit
that referenced
this issue
Aug 9, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I don't quite understand what is going on with the following decompiled expression.
this => IIF(this.HasBar, this.Posts.Any(x => True), (this.HasBaz AndAlso this.Posts.Any((x => True ?? x => True))))
More specifically, this part is perplexing.
this.Posts.Any((x => True ?? x => True))
I'm assuming it should only be
this.Posts.Any(x => True)
My basis for this assumption is if you change the
||
to just|
, then it works fine.When using that expression in conjunction with EFCore/Remotion.LINQ, those libraries fail to parse the expression and throw an exception. I don't know where the actual problem lies. Any help would be appreciated.
Here is the code.
The text was updated successfully, but these errors were encountered: