[!277] Add a first implementation of hooks
Merge branch 'feature/code-generation-hooks' into 'master' ref:dominic/dune-perftool This is the first minimal implementation of how code generation hooks from downstream projects could look like. There is a few more things to think about (feel invited to share ideas): - \[x\] How to document the arguments and return values expected from hooks - \[x\] How to handle multiple hooks registered to the same hook point and return values (this is quite relevant once you want to do loopy transformations in a hook. It means that you want to "chain" the hooks) This fixes [#129]. See merge request [dominic/dune-perftool!277] [#129]: gitlab.dune-project.org/NoneNone/issues/129 [dominic/dune-perftool!277]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/277 Closes #129
No related branches found
No related tags found
Showing
- python/dune/perftool/generation/__init__.py 5 additions, 0 deletionspython/dune/perftool/generation/__init__.py
- python/dune/perftool/generation/hooks.py 53 additions, 0 deletionspython/dune/perftool/generation/hooks.py
- python/dune/perftool/pdelab/localoperator.py 11 additions, 0 deletionspython/dune/perftool/pdelab/localoperator.py
- python/dune/perftool/ufl/preprocess.py 5 additions, 0 deletionspython/dune/perftool/ufl/preprocess.py
python/dune/perftool/generation/hooks.py
0 → 100644
Please register or sign in to comment