Steven Troxler

Interesting - I recently tried to get the debugger working, and I actually didn't run into this problem on the bytecode *executable*, but I did run into it if I...

Pyre infer does have a `--simple-annotations` flag that only adds annotations which wouldn't require an import. Would that be enough to solve your problem? It might not, since Pyre could...

I would very much favor that `__new__` and `__init__` be treated as special cases and exempt from strict `@override` checks - most type checkers (or at least Pyre) do not...

I don't have as much of an opinion about multiple inheritance; that's a messy problem that I haven't thought too much about. In many cases preexisting conventions (which vary a...

This sounds quite nice. There should be no need for a join, at least depending on what we mean by "join"... the axis that would need the same label would...

Hi @vthemelis sorry I hadn't been following this PR, I'll try to see what's blocking it next week. But regardless, I think given that the Pyre team has not been...

@sumersao off I'm sorry to hear that. There is not currently a way to set a timeout. There are ways to make Pyre not type check the code in question...

Closing the loop on this: I backed all these out to only use `Union`. We cannot make use of `from __future__ import annotations` because this code is using the types...

Hi @henrylhtsang. Unfortunately, there's an architectural issue in Pyre (and a number of other tools too) where we assume that a fully qualified name means something unambiguous in Python, so...

(You can of course use a `# pyre-ignore` to suppress the error you are seeing, but unfortunately users of your library who are using Pyre - which includes most Meta...