Jukka Lehtosalo
Jukka Lehtosalo
To get a better idea of how big the impact might be, it would be interesting to see some statistics about how frequently this could be used in some non-trivial...
This isn't supported right now. It shouldn't be hard to make it work, though, if somebody wants to give it a try.
We wouldn't need to support `[builtins ...]`, which specifies a fairly minimal test-only stub to use for a particular mypy test case. These tests could probably use the real stubs...
I'd suggest using whatever stubs each tool is shipped with. For mypy this would be typeshed, but other tools might use custom stubs for builtins, for example.
Parsing `.test` files is actually pretty simple -- most of the related code is about creating files related to test cases, cleaning them up and handling various special cases that...
@pranavrajpal So would be have `Value[T]` where `T` is based on the rtype of the value? This may be tricky, since there are various types that can be implicitly coerced...
I think that the cleanest way to implement this would be as a separate optimization pass.
It turns out that writing an optimization pass that modifies IR with our current IR representation is kind of messy. Doing this during IR build instead would also be reasonable....
No cleanup of literals is required any more, since after #794 we collect literals in a later pass. Also we now have a cleaner IR, so writing this as a...
I will be doing this during IR build, since it looks easier. It might also be useful to actually have some constant folding to happen during type checking, or at...