[Mlir-commits] [mlir] [mlir] Add the concept of ASM dialect aliases (PR #86033)

[Markus Böck]

zero9178 wrote:

I am curious about the motivation. Have you considered other options such as the equivalent of `getDefaultDialect` of `OpAsmInterface`? 
On first glance this seems like a too powerful option that could cause a great deal of confusion (and potentially ambigiouty?) that proably requires an RFC. A less powerful implementation that satisfies your use-case would probably be nicer. Is my understanding correct that the printer currently allows arbitrary strings to be printed? 
For some of the tests I can see a less powerful dialect (or ODS?) hook that'd allow something like `!test.tensor_int3<IntType>` to map to `tensor<3xIntType>`. In fact, this is already possible today if a user overwrites `Dialect::parseAttribute` instead of using the default ODS generated implementation.

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