-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Fall out from #36502 #36550
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
Fall out from #36502 #36550
Conversation
42b6a82
to
6c7feaa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, LGTM modulo some nits!
src/EFCore.Relational/Query/Internal/RelationalProjectionBindingExpressionVisitor.cs
Outdated
Show resolved
Hide resolved
src/EFCore.Relational/Query/Internal/RelationalProjectionBindingExpressionVisitor.cs
Outdated
Show resolved
Hide resolved
96611a5
to
79c139b
Compare
e273964
to
a85a356
Compare
|
||
/// <inheritdoc /> | ||
public override StructuralTypeShaperExpression MakeClrTypeNullable() | ||
=> Type != Type.MakeNullable() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know you're just following the common pattern here (that's good), but I've never understood why the inverse conditional logic, i.e. why not do:
=> Type == Type.MakeNullable()
? this
: new RelationalStructuralTypeShaperExpression(StructuralType, ValueBufferExpression, IsNullable, MaterializationCondition, Type.MakeNullable());
One day I'll do a pass...
No description provided.