diff options
| author | Mehdi Amini <joker.eph@gmail.com> | 2021-10-20 19:51:52 +0000 |
|---|---|---|
| committer | Mehdi Amini <joker.eph@gmail.com> | 2021-10-26 07:21:09 +0000 |
| commit | f431d3878a07a67e544dacb98ad553b6a0b6b25a (patch) | |
| tree | e854577a0aedf7409520c4d8acaf6636f8fe8377 /lldb/source/Commands/CommandObjectPlatform.cpp | |
| parent | 4c8ea90b252eeead9a6943f67444a229147949fb (diff) | |
| download | llvm-f431d3878a07a67e544dacb98ad553b6a0b6b25a.zip llvm-f431d3878a07a67e544dacb98ad553b6a0b6b25a.tar.gz llvm-f431d3878a07a67e544dacb98ad553b6a0b6b25a.tar.bz2 | |
Make Python MLIR Operation not iterable
The current behavior is conveniently allowing to iterate on the regions of an operation
implicitly by exposing an operation as Iterable. However this is also error prone and
code that may intend to iterate on the results or the operands could end up "working"
apparently instead of throwing a runtime error.
The lack of static type checking in Python contributes to the ambiguity here, it seems
safer to not do this and require and explicit qualification to iterate (`op.results`, `op.regions`, ...).
Reviewed By: ftynse
Differential Revision: https://reviews.llvm.org/D111697
Diffstat (limited to 'lldb/source/Commands/CommandObjectPlatform.cpp')
0 files changed, 0 insertions, 0 deletions