Expose new integer methods #153
Merged
Conversation
This file contains hidden or 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
pontusmelke
force-pushed
the
1.1-integer-cleanup
branch
from
0e6d510 to
8d0e9ea
Compare
Expose `inSafeRange`, `toNumber`, and `toString` in order to facilitate integer handling.
It does not make sense to expose the `Integer` type to users. Users should use a framework of their liking instead and we only expose `inSafeRange`, `toNumber` and `toString` functions.
pontusmelke
force-pushed
the
1.1-integer-cleanup
branch
from
8d0e9ea to
a414253
Compare
This was referenced Nov 21, 2016
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.
inSafeRange,toNumber, andtoStringin order tofacilitate integer handling.
Integer: It does not make sense to expose theIntegertype to users. Users should use a framework of their liking instead and we only exposeinSafeRange,toNumberandtoStringfunctions.