You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With 4770b78, the #[format_op] supports specifying attributes in an Op in the syntax, using $attr_name.
This prints (or parses) an AttrObj and gets / sets the corresponding the attribute in the Op. A minor downside of this is that, because we're printing / parsing a general AttrObj, the attribute's attr_id also must be / is printed (so that we know what attribute to parse). A way to avoid this is to allow specifying via a format directive, such as attr($attr_name, "::path::to::concrete::type"). With this, we can generate a printer / parser without the attr_id needing to be part of the syntax.
The text was updated successfully, but these errors were encountered:
With 4770b78, the
#[format_op]
supports specifying attributes in anOp
in the syntax, using$attr_name
.This prints (or parses) an
AttrObj
and gets / sets the corresponding the attribute in theOp
. A minor downside of this is that, because we're printing / parsing a generalAttrObj
, the attribute'sattr_id
also must be / is printed (so that we know what attribute to parse). A way to avoid this is to allow specifying via a format directive, such asattr($attr_name, "::path::to::concrete::type")
. With this, we can generate a printer / parser without theattr_id
needing to be part of the syntax.The text was updated successfully, but these errors were encountered: