[Mlir-commits] [llvm] [mlir] [mlir][Python] create MLIRPythonSupport (PR #171775)
Maksim Levental
llvmlistbot at llvm.org
Mon Dec 29 07:28:43 PST 2025
makslevental wrote:
> but it does make me question the assertion that it has to be shared.
The current bazel just rebuilds everything as it was before. So sure if you don't intend to use the CRTPs in your own dialect extensions (ever...) nor do you use any of the existing dialect extensions (which I will port in follow-up PRs) then this is NFC for you. But my plan is indeed to deprecate `mlir_pure_subclass` so eventually you will have to use these CRTPs...
The test of whether your downstream build is actually compatible is whether `PythonTestNanobind` builds successfully and the corresponding test succeeds.
https://github.com/llvm/llvm-project/pull/171775
More information about the Mlir-commits
mailing list