It seems like interface definitions don't use the MLIR_DECLARE_EXPLICIT_TYPE_ID macro, and so rely on the implicit fallback mechanism to allocate storage for their TypeId. This seems like an oversight to me, and should be easy to fix, although there might be some technical reason for how it works right now.
It seems like interface definitions don't use the `MLIR_DECLARE_EXPLICIT_TYPE_ID` macro, and so rely on the implicit fallback mechanism to allocate storage for their TypeId. This seems like an oversight to me, and should be easy to fix, although there might be some technical reason for how it works right now.
It seems like interface definitions don't use the
MLIR_DECLARE_EXPLICIT_TYPE_ID
macro, and so rely on the implicit fallback mechanism to allocate storage for their TypeId. This seems like an oversight to me, and should be easy to fix, although there might be some technical reason for how it works right now.