Better shorthand for units #7
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adamchalmers
force-pushed
the
achalmers/unit-aliases
branch
from
2852c9b to
c41bce9
Compare
|
Why is the I also believe having too many ways to express the same thing is just confusing. |
|
Reminds me of https://en.cppreference.com/w/cpp/language/user_literal |
|
More prior art:
|
|
Not sure where else to put this, but the maintainer of dimensional, the Haskell package, just posted this: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
My proposal: these are all valid KCL expressions for the same value.
Distance.Meter(1)-- fully spelled out, using normal KCL syntax.1.Meter-- using "unit suffix" notation, which is syntactical sugar (aka shorthand) for the above1.m-- very commonly-used units have a second, shorter unit suffix.Thanks to @lf94 for suggesting this!