[Mlir-commits] [mlir] [mlir][py] invalidate nested operations when parent is deleted (PR #93339)

[Stella Laurenzo]

stellaraccident wrote:

> This is workable I think? It allows people to control their exposure by narrowing and widening the scope (i think?).

As long as there is a mode that lets me not do that. In the order of priorities for these bindings, the primary use case is IR construction. The secondary use case is what I've been calling "lightweight IR" traversal. A third is trying to implement some kind of compiler framework in Python, but I would argue strongly that this use case in generality is in conflict with the first two and if serious about it, we would be better off having two bindings.

The first and second use cases could be well served by some kind of safety scoping arena, as long as it wasn't required for use: there are plenty of cases where there is no bounding stack context for such things.

https://github.com/llvm/llvm-project/pull/93339