Further enforce template consistency

Issue/feature addressed

• Consistently use default_fp_type instead of mixture of default_fp_type, double or NekDouble.
• Use a single definition of default_fp_type = double
• Use TData instead of double or NekDouble, when appropriate

Proposed solution

Implementation

Tests

Suggested reviewers

Please suggest any people who would be appropriate to review your code.

Notes

Please add any other information that could be useful for reviewers.

Checklist

• Functions and classes, or changes to them, are documented.
• [ ] User guide/documentation is updated.
• [ ] Changelog is updated.
• Suitable tests added for new functionality.
• Contributed code is correctly formatted. (See the contributing guidelines).
• [ ] License added to any new files.
• No extraneous files have been added (e.g. compiler output or test data files).

added mergeredesign label

marked the checklist item Functions and classes, or changes to them, are documented. as completed

marked the checklist item Suitable tests added for new functionality. as completed

marked the checklist item Contributed code is correctly formatted. (See the contributing guidelines). as completed

marked the checklist item No extraneous files have been added (e.g. compiler output or test data files). as completed

changed the description

added 3 commits

• 08fb6f96...5ed55e2e - 2 commits from branch nektar:feature/redesign
• 00cacffc - Merge remote-tracking branch 'origin/feature/redesign' into...

Compare with previous version

marked this merge request as ready

enabled an automatic merge when all merge checks for 00cacffc pass

mentioned in commit dd84cb8f

merged