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 think it's a cool idea but the mref() annotation should be done through a static analysis check instead of in the type system.
By doing it in the type system, it forces function/method overloads when receiving const T& or T& in a template where the distinction matters. Overloading is against the principles. For example in Option:
I think it's a cool idea but the mref() annotation should be done through a static analysis check instead of in the type system.
By doing it in the type system, it forces function/method overloads when receiving
const T&
orT&
in a template where the distinction matters. Overloading is against the principles. For example in Option:Keep
mref()
sIn anticipation of a static check, keep the mref() annotations that we have, but make it a function
The text was updated successfully, but these errors were encountered: