Process attributes after Qed/Defined#22118
Conversation
|
@SkySkimmer What should the next steps here be?
I'm happy to put more cycles into the development. |
That seems fine, there doesn't seem to be a way to get the error earlier anyway.
I don't see the point of having it be a plugin, it seems like it should be in the statically linked part. But do it as a separate PR since it has much more bikeshed potential. |
110bc01 to
3034b35
Compare
|
I have removed the plugin code from the PR. |
|
@coqbot run full ci |
3034b35 to
154d476
Compare
154d476 to
40e8800
Compare
|
@coqbot run full ci |
|
@SkySkimmer Do you want me to add a changelog entry? Is there anything else that needs to happen to get this merged? |
|
I don't think we have any attributes defined with this system currently so there should be no user visible change right? (which is why you need a custom plugin for testing) |
|
@coqbot merge now |
This PR extends the handling of attributes so that handlers are executed when the term is completed, e.g. at the
QedorDefined.It uses this feature to implement a plugin that provides an attribute
#[hint(db=...,cost=...,visibility=...)]. This should be either incorporated into core Rocq or introduced as a separate plugin.For now, I'm just looking for feedback, the commits should be independently reviewable. The last commit contains the hint attribute implementation and could probably use more testing.