Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix t.Set undefined type spurious error
Summary: Looks like the latest binary release has fixed one part of the original issue - previously, `from typing import Set` would not throw this spurious error while `import typing as t` and referencing `t.Set` would. Now, it's boiled down to a pretty clear issue where we are looking up the annotation `typing.Set` and cannot find it in the type hierarchy. Looking a little closer, we `typing.Set` is not in our class hierarchy because `set` is, and we map the equivalence for other types like `typing.List -> list` in Type create. Adding this mapping fixes this issue. typing.pyi: https://github.com/python/typeshed/blob/master/stdlib/3/typing.pyi class hierarchy from env with typeshed included: P142551722 Reviewed By: grievejia Differential Revision: D23726491 fbshipit-source-id: 15db093f5be6222b02ff4c4f3ae7ba221c3d82fc
- Loading branch information