How to extend the tensor toolbox - Test "new subsequent modules" #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Test "new subsequent modules"
As "forewarned" in the LS-Dyna example pull request, I tested the approach to add new modules to extend the functionality for specific use cases (not yet documented).
So besides the essential module "Tensor", I created the module "TensorXLSDYNA" as an e"X"tension of "Tensor" for LS-Dyna (lack of creativity duly noted). It works quite well. We require an additional "include" (I forgot this in the LS-Dyna example, of course, as you said "a single include and use statement is shorter than two") and "use TensorXLSDYNA".
Just see this as a test of a possible way for the ttb extension. I would prefer something that links the modules closer, e.g. some inheritance. But how to incorporate this?