| Issue |
55380
|
| Summary |
[AsmParser QoI] Improve "expected attribute value" diagnostic
|
| Labels |
mlir:core
|
| Assignees |
|
| Reporter |
lattner
|
The asmparser diagnostics are getting better, we now generate `expected attribute value` in cases that want integer constants etc instead of complaining about function types.
I wonder if we can do better though: parseAttribute takes an optional type, and if we know we're looking for a value of integer type, we could give a more specific "expected integer value" diagnostic.
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
