Use constants instead of types from typenum to describe units #96
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.
Two major advantages
Quantity<_, SIUnit<3, 2, -1, 0, 0, 0, 0>>rather than the typenum gibberish. Not completely self explanatory, but should be much easier to spot errors.METER.powi::<P2>()becomesMETER.powi::<2>(), so no need to import the obscuretypenum::P2Disadvantage
Once const_generics can be used in operators the boilerplate can be simplified a lot without even breaking the code (I think).