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's mainly an artifact of history, since Float came first, and it's a breaking change to add a super trait.
I think it would also cause method resolution ambiguity in the current state, since any T: Float context would have multiple overlapping method names in scope. If we ever do make that breaking change, Float should only add distinct methods over its super traits.
Is there a reason that
Float
doesn't haveFloatCore
andReal
as super traits?The text was updated successfully, but these errors were encountered: