-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use i64, and allow trivial_numeric_casts #7
Merged
Merged
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
The traits are implemented from 64-bit values, and we don't want to lose any bits when comparing on platforms with smaller `isize`.
Simple enum expressions may have no explicit type, like `A = 1`, so then the derived `1 as i64` is inferred like `1i64 as i64`, a trivial numeric cast. But it's quite possible that other expressions could have explicit types, so we can't just assign it directly either. The simple solution is to just allow the `trivial_numeric_casts` in derived code.
great job! |
Thanks for checking it! bors r+ |
bors bot
added a commit
that referenced
this pull request
Jan 23, 2018
7: Use i64, and allow trivial_numeric_casts r=cuviper a=cuviper The traits are implemented from 64-bit values, and we don't want to lose any bits when comparing on platforms with smaller `isize`. Simple enum expressions may have no explicit type, like `A = 1`, so then the derived `1 as i64` is inferred like `1i64 as i64`, a trivial numeric cast. But it's quite possible that other expressions could have explicit types, so we can't just assign it directly either. The simple solution is to just allow the `trivial_numeric_casts` in derived code. Fixes #6.
Wait, I didn't check it yet :) Going to do it now. Yep, it does! 🎉 |
Build succeeded |
Oops. :) I'll wait for you before I publish anything... |
@cuviper see edit :) I actually was going to sleep, but your response has waken me up 😄 P.S. Shouldn't we update version? |
(quietly) num-traits 0.1.43 is published -- good night! |
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.
The traits are implemented from 64-bit values, and we don't want to lose
any bits when comparing on platforms with smaller
isize
.Simple enum expressions may have no explicit type, like
A = 1
, so thenthe derived
1 as i64
is inferred like1i64 as i64
, a trivial numericcast. But it's quite possible that other expressions could have explicit
types, so we can't just assign it directly either. The simple solution is
to just allow the
trivial_numeric_casts
in derived code.Fixes #6.