This repository has been archived by the owner on May 26, 2021. It is now read-only.
Bugfix: Inverting a TimeUnitQuantity gave the answer as time, not frequency #172
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
…ot frequency units.
|
On hold pending #173. |
This was referenced Aug 11, 2017
Merged
keilw
added a commit
that referenced
this pull request
Aug 11, 2017
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Also added a unit test. Note that diff stats for this change are greatly exaggerated; the only methods I've actually touched are TimeUnitQuantity.inverse() and TimeQuantitiesTest.inverseTest(). Is this repo handling whitespace abnormally?