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
Auto-borrowing or auto-dereferencing are confusing me here, but this feels somewhat weird and inconsistent.
I wonder why all the operator overloads need to implemented methods rather than associatied functions where all the operands could be equally unsurprising arguments and not half arguments, half method receivers, but I'm not sure how applicable that is to this nitpick.
The text was updated successfully, but these errors were encountered:
Related to #4920. My proposal is to make == and other operators never do any form of auto-coercion.
I am also inclined to agree associated fns would be better than methods but it doesn't really make any difference to the question at hand, which is what the behavior should be when used as binary operators.
Auto-borrowing or auto-dereferencing are confusing me here, but this feels somewhat weird and inconsistent.
I wonder why all the operator overloads need to implemented methods rather than associatied functions where all the operands could be equally unsurprising arguments and not half arguments, half method receivers, but I'm not sure how applicable that is to this nitpick.
The text was updated successfully, but these errors were encountered: