Merge dune-geometry with dune-common?
I propose to drop dune-geometry and merge its contents with dune-common.
Arguments coming to my mind:
- It would reduce the number of core modules. So less modules to checkout, update, configure & build, test, upload etc.
- With most of the C++11 compatibility code gone from dune-common, there is not too much left beside the build-system.
- Who wants to use dune-geometry without dune-common? Even if someone insists on doing so, dune-geometry is not that heavy-weight to be an obstacle.
- We would get rid of the name clash of having a module called geometry and a class in dune-grid called
Geometry
. This is no longer relevant, as we won't introduce namespaces.
Such a simplification would be suitable for Dune 3.0. I don't think we would lose modularity.
What do you think?