Skip to content

Commit cd8fc46

Browse files
committed
docs: add prop-dict to Custom Directives documentation
`prop-dict` is supported in custom directive since #77061 but documentation was not added here
1 parent 82a6d2f commit cd8fc46

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

mlir/docs/DefiningDialects/Operations.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -887,11 +887,12 @@ declarative parameter to `parse` method argument is detailed below:
887887
- Variadic: `SmallVectorImpl<Type> &`
888888
- VariadicOfVariadic: `SmallVectorImpl<SmallVector<Type>> &`
889889
* `attr-dict` Directive: `NamedAttrList &`
890+
* `prop-dict` Directive: `OperationState &`
890891

891892
When a variable is optional, the value should only be specified if the variable
892893
is present. Otherwise, the value should remain `None` or null.
893894

894-
The arguments to the `print<UserDirective>` method is firstly a reference to the
895+
The arguments to the `print<UserDirective>` method are firstly a reference to the
895896
`OpAsmPrinter`(`OpAsmPrinter &`), second the op (e.g. `FooOp op` which can be
896897
`Operation *op` alternatively), and finally a set of output parameters
897898
corresponding to the parameters specified in the format. The mapping of
@@ -921,6 +922,7 @@ declarative parameter to `print` method argument is detailed below:
921922
- Variadic: `TypeRange`
922923
- VariadicOfVariadic: `TypeRangeRange`
923924
* `attr-dict` Directive: `DictionaryAttr`
925+
* `prop-dict` Directive: `FooOp::Properties`
924926

925927
When a variable is optional, the provided value may be null. When a variable is
926928
referenced in a custom directive parameter using `ref`, it is passed in by

0 commit comments

Comments
 (0)