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
That would be pretty awkward to implement because we usually distinguish expression-based unification from typed-based unification purely by context. With something like this we would have to try the expression-based approach and if we come across a casting field that isn't marked with @:using we would have to fall back. And that also raises more questions, like should the fallback attempt to find other casting fields which might have a @:using or should it go straight to type-based unification?
I wonder if we should instead simply always use expression-based unification for anything that is brought into context via @:using. But somebody has to think that through as well.
Adding something like @:using could fix the current incompatibility between the static extensions and implicit casts.
This is related to: #5924
The text was updated successfully, but these errors were encountered: