Michael J. Sullivan

PR #7829 makes all `name` and `fullname` methods in mypy into properties. This will unfortunately require changes to many plugins. We've decided that it is worth removing a long-standing pain...

Unfortunately mypy doesn't support subclassing `property` right now. In simple use-cases, you can get away with something like ``` if TYPE_CHECKING: CustomProperty = property else: # real CustomProperty definition ```...

Inlining a lot more with our current backend hurts compile time a bunch too

https://github.com/mypyc/mypyc/issues/450 is related

> As far as I've considered, I think this would match the idea. However, I am not sure for ops like `list * int`, since its C implementation does not...

I started doing this, to pass the time while I waited for gcc to try to compile most of mypy. Turns out that the biggest thing by far was "initializing...

@vpetrovykh Could you look into this and see if there's anything that can be untangled? Either both should work or both shouldn't. Honestly probably both shouldn't work, but we might...

Thing one is isn't actually an Internal Server Error. It's a proper error with source location information and an error message. I think it is arguably actually intended behavior, but...

A workaround for thing one is to wrap the conditions of the `if` statements in a set literal, like ``` if {question is B_Question and color = Color.Red and not...

Yeah there are a lot of similar errors we should detect at create time. We should also probably avoid the QualName turd