Add typing generics

[schnellerhase]

Extends the approach of #4094 for multi export type wrappers to

• Vector
• MatrixCSR
• SuperLUDistMatrix
• SuperLUDistSolver
• DirichletBC
• CoordinateElement
• FiniteElement
• Form
• Constant
• Expression
• Function
• FunctionSpace
• Mesh
• Geometry
• CoordinateElement
• BoundingBoxTree
• PointOwnershipData

Depends on #4135

[jhale]

Looks good - have you considered directly mimicking the naming/setup of the C++ concepts? Perhaps they could also be put somewhere more general for use across the whole interface.

https://github.com/FEniCS/dolfinx/blob/main/cpp/dolfinx/common/types.h#L26

[schnellerhase]

Looks good - have you considered directly mimicking the naming/setup of the C++ concepts? Perhaps they could also be put somewhere more general for use across the whole interface.

https://github.com/FEniCS/dolfinx/blob/main/cpp/dolfinx/common/types.h#L26

AFAIK the python typing currently does not allow conditional type deductions, so we can not mimic any scalar/real type concepts.

[jhale]

I think you're overcomplicating it a bit. My basic point is to add a dolfinx.typing module where you add meaningful definitions of e.g. _Scalar and _Float using TypeVar and then import them uniformly for use elsewhere. Perhaps some modules where the definition is isolated (e.g. MeshTags) the current design is appropriate.

[jhale]

This should be merged when:

• Makefile is removed.
• Comment above on adding dolfinx.typing is responded to/addressed.