Jukka Lehtosalo

We could also make `LoadInt` a direct subclass of `Value`, similar to `Register`. This would simplify things a bit, since we'd no longer need the `find_constant_integer_registers` business, and generating IR...

The current state seems pretty good to me already, so I'm marking the remaining work as low priority.

Can you try the latest development wheels from here: https://github.com/mypyc/mypy_mypyc-wheels/releases We made some changes to the wheel builds recently, and I'm not sure if 0.812 include them. If they work,...

Thanks for trying the dev wheels! Here's a copy of the traceback: ``` Traceback (most recent call last): File "crash.py", line 2, in from mypyc.build import mypycify File "mypyc\build.py", line...

It would be useful to have some more information to narrow this down: * Does this only impact Python 3.5/3.6 (do things work on 3.7+)? (Note that the next release...

> directly create instances of traits. Even if we can support this, I'm not sure if I'd want to. I think of traits as variants of ABCs, and as such...

@ilevkivskyi That sounds reasonable, though the name 'trait' would become more confusing. I wonder if we can figure out a better name for traits. Logically these would be "multiple inheritance...

@DunderBird Good analysis! We should try to remain compatible with CPython here. I.e., we should add the identity check in the generated code if CPython uses it. So `b in...

A relatively simple approach would be to special case `str` vs. `Iterable[str]` / `Sequence[str]` compatibility in a type checker. This behavior could be enabled through a strictness option. This issue...

> Maybe Text could be a Protocol that has the same methods as Sequence except for one? Unfortunately this would make `Text` incompatible with `str` and would generally break typeshed...