-
-
Notifications
You must be signed in to change notification settings - Fork 231
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
Issue: Implicitly conversion from a non-nullable value type to the nullable form of that value type is broken? #188
Comments
Can you please post a full project example for dotnet core / normal .net ? |
@StefH |
Thanks. I'm able to reproduce and I've fixed it. Now I need to add some unit-tests. You can already take a look here: |
👍 |
I'll create a new NuGet in some time. |
See https://github.com/StefH/System.Linq.Dynamic.Core/wiki/Dynamic-Expressions#conversions
Or I misused this in an not proper way?
Hit this issue with debug an query issue with efcore when eval at local, and it's able to write an reproduct case without efcore. Tested with
1.0.8.11
Update: This get null on netcoreapp, and an
System.Security.VerificationException:“操作可能会破坏运行时稳定性。”
(Operation may break runtime stability
) on netfxThe text was updated successfully, but these errors were encountered: