Bas van Beek comments

Results 59 comments of


                                            Bas van Beek

Allow `init` and `new` to return `NoReturn`

Any idea what's going on with the failed `Run mypy_primer / Run (2)` Test? It looks like it crashed while installing depencies or something.

Allow `init` and `new` to return `NoReturn`

Let's give it a shot (note: I might need approval again as a first-time contributor)

Allow `init` and `new` to return `NoReturn`

So, are there any further comments on this PR?

Allow `init` and `new` to return `NoReturn`

Closing and re-opening as no CI runs appear to be starting.

Allow `init` and `new` to return `NoReturn`

> Closing and re-opening as no CI runs appear to be starting. Right, that's better. This PR does still need approval after the latest `master` branch rebase. > Please let...

Allow `init` and `new` to return `NoReturn`

Rebased to get rid of another merge conflict. For future reference, is there a preference for either rebasing or updating from master when dealing with merge conflicts?

AnyOf - Union for return types

Two more cases wherein `AnyOf` would be very useful: Dealing with overload ambiguity -------------------------------- ``` python @overload def func(a: Sequence[int]) -> str: ... @overload def func(a: Sequence[str]) -> int: ......

Now overloads with ambiguous `self` are handled properly

Nice! It seems this PR fixes most of the issues. One case that does still seem to fail is when `Foo[Any]` subclasses are involved: ``` python from typing import Generic,...

Now overloads with ambiguous `self` are handled properly

> @BvB93 I think that this is unrelated. Because it would require a change in how has_any_type works. And it can backfire in lots of places. But, please open a...

Now overloads with ambiguous `self` are handled properly

Out of curiosity, is there a particular reason why this has PR stalled?