New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should check nested functions #61
Comments
Hi @PeterJCLaw, thanks for the report. |
@dark Thanks! Is there a list of known limitations somewhere, to save us reporting (and you having to triage) known limitations? |
Unfortunately we don't have such a list in the repo. We should add one. |
This feature has been implemented a while ago, I had forgot to ping this task. The example above now triggers errors on all relevant lines. |
Nice, thanks for fixing 😊 |
Summary: Several fixes: - one of the examples bothered me because the okay and bad case were not the same (3 vs 2 type variables) in a way that didn't highlight the point (don't repeat type variables) - other than that, mostly trying to get consistent style: - 4 spaces, not 2 (unfortunately editors often do 2 by default on markdown, which is presumably why we keep getting 2-spaced python code) - always have a blank line between functions - make any typing imports explicit (this is debateable but most of our existing examples do it, so it's good to be consistent) - 2 spaces before comments Reviewed By: grievejia Differential Revision: D29690381 fbshipit-source-id: 47876f06d4ffa4a458d5fb22198ee91127c38ceb
python
: 3.5.2, 3.6.5pyre
: 0.0.7 (frompip list
)Given a file
thing.py
:I'd expect to get errors from the bad types in the nested
inner
function. For reference, here's whatmypy
(0.600) outputs:Yet while
pyre
does not find errors in the top level equivalent functionouter_inner
, it doesn't emit any errors about the nested function:The text was updated successfully, but these errors were encountered: