Options for a long term fix of the special case for float/int/complex

[Liz (Elizabeth King)]

Can we get discussion on this going again?

If we’re allowing this to be expressed, one of these has to happen with either the use of negation or un-special casing it.

@Liz

@overload
def y(a: float & ~int, b: float & ~int) -> float & ~ int:  ...
@overload
def y(a: float & ~int, b: float) -> float & ~ int:  ...
@overload
def y(a: float, b: float & ~int) -> float & ~ int:  ...
@overload
def y(a: int, b: int) -> int:  ...

I think it’s clearly better and more friendly to work toward seperating these rather than entangling more complexly than they already are.

Here’s what it would look like with these meaning what they actually are at runtime:

@overload
def y(a: float , b: float) -> float:  ...
@overload
def y(a: int, b: float) -> float:  ...
@overload
def y(a: float, b: int) -> float:  ...
@overload
def y(a: int, b: int) -> int:  ...

I think it’s pretty clear that one of these is more natural than the other.