You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm debating whether or not to have foo.eq(None) result in foo IS NULL or not. Either way, for ergonomics, we should allow foo.eq("bar") in addition to foo.eq(Some("bar")). At the moment, attempting to write this ToSql implementation results in overlap both with the impl for Option<T>, and for &'a T. I think we need specialization for this to work.
The text was updated successfully, but these errors were encountered:
I'm debating whether or not to have
foo.eq(None)
result infoo IS NULL
or not. Either way, for ergonomics, we should allowfoo.eq("bar")
in addition tofoo.eq(Some("bar"))
. At the moment, attempting to write thisToSql
implementation results in overlap both with the impl forOption<T>
, and for&'a T
. I think we need specialization for this to work.The text was updated successfully, but these errors were encountered: