Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use Subscript-compatible logic for
__setitem__
in typeCheck.ml
Summary: In order to make it easy to roll out the sweeping changes when I add a Subscript node to the AST and cut over `__getitem__` in the parser, I first want to make sure existing uses of the `special = true` `__getitem__` are always handled in a way that is: - distinct from the "vanilla" `Expression.Call` case - compatible with what Subscript will get us, which is just `base` and `index` (so basically, don't use the `callee` or other parts of the `__getitem__` `Call` node that won't exist after cutting over) This diff makes that change in the part of `typeCheck.ml` where we are handling subscript assignment targets: only rely on `base` and `index` here when constructing synthetic `__setitem__` call data, so that we'll be able to just drop in a `Subscript` match with the same body. Reviewed By: yangdanny97 Differential Revision: D57113190 fbshipit-source-id: c03e595a7c4a33bc910a0de32b73e57a51436e65
- Loading branch information