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

Merge branch 'feature/more-avoiding-of-noop-conditionals' into 'master'

ref:dominic/dune-perftool By looking at the possible values of the condition.

See merge request [dominic/dune-perftool!281]

  [dominic/dune-perftool!281]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/281

By looking at the possible values of the condition.

Merge branch 'feature/avoid-visiting-noop-integrals' into 'master'

ref:dominic/dune-perftool I have a case where visiting has a side effect that
I want to avoid. Also spares work.

See merge request [dominic/dune-perftool!280]

  [dominic/dune-perftool!280]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/280

I have a case where visiting has a side effect that I want to avoid.
Also spares work.

Merge branch 'feature/allow-custom-ufl-types' into 'master'

ref:dominic/dune-perftool We do want code bloat in dune-perftool for the
specific needs of a given application. We therefore allow custom UFL nodes to
procide their own visitor implementation. This was done previously for the
very specific case of a MathFunction node, but it can be done with any node.

See merge request [dominic/dune-perftool!278]

  [dominic/dune-perftool!278]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/278

Merge branch 'feature/remove-obsolete-argument-from-boundary-predicates' into 'master'

See merge request [dominic/dune-perftool!279]

  [dominic/dune-perftool!279]: Nonedominic/dune-perftool/merge_requests/279

Merge branch 'feature/dont-generate-jacobian-for-matrix-free' into 'master'

See merge request [dominic/dune-perftool!272]

  [dominic/dune-perftool!272]: Nonedominic/dune-perftool/merge_requests/272

Merge branch 'feature/cmake-allow-more-generation-dependencies' into 'master'

ref:dominic/dune-perftool I have the use case of a boundary condition file,
whose changes should retrigger the code generation process.

See merge request [dominic/dune-perftool!275]

  [dominic/dune-perftool!275]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/275

Merge branch 'feature/use-different-dof-numbers-for-cg' into 'master'

ref:dominic/dune-perftool I'm not 100% sure this gives the right number of
dofs for parallel applications, but at least for serial applications it is
correct.

See merge request [dominic/dune-perftool!274]

  [dominic/dune-perftool!274]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/274

Merge branch 'feature/nonlinear-sumfact-cg' into 'master'

ref:dominic/dune-perftool Contains [!264] and master\....

See merge request [dominic/dune-perftool!269]

  [!264]: gitlab.dune-project.org/NoneNone/merge_requests/264
  [dominic/dune-perftool!269]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/269

Merge branch 'feature/sum-factorization-gmsh-files' into 'master'

ref:dominic/dune-perftool On unstructured grids we need to make sure that the
quadrature points on intersections on neighboring cells are visited in the
same order. This is done using edge consistent grids and by constructing the
geometry mappings in the right way.

Still missing:

-   Vectorization
-   Make UG grids edge consistent without writing and reading a gmsh file

See merge request [dominic/dune-perftool!264]

  [dominic/dune-perftool!264]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/264

I have the use case of a boundary condition file, whose changes should retrigger
the code generation process.

This options enables to generate jacobian apply methods regardless
of the `matrix_free` option. If `matrix_free` is set to true,
`generate_jacobian_apply` is also set to true. This option replaces
`matrix_free` in all contexts except in the selection of the solver.

Needed in dune-perftool-playground for Navier stokes

There seems to still be some problem.

Merge branch 'feature/better-subdomain-handling' into 'master'

See merge request [dominic/dune-perftool!268]

  [dominic/dune-perftool!268]: Nonedominic/dune-perftool/merge_requests/268

Note: Not yet working for gmsh files

Merge branch 'feature/lambda-generation-with-more-geometry' into 'master'

Target: normal-dependent constraints assembly.

See merge request [dominic/dune-perftool!267]

  [dominic/dune-perftool!267]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/267