-
Notifications
You must be signed in to change notification settings - Fork 34
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
Construct Value only from uint32_t/uint64_t #746
Conversation
Codecov Report
@@ Coverage Diff @@
## master #746 +/- ##
==========================================
- Coverage 99.26% 99.26% -0.01%
==========================================
Files 74 74
Lines 11442 11439 -3
==========================================
- Hits 11358 11355 -3
Misses 84 84
Flags with carried forward coverage won't be shown. Click here to find out more.
|
lib/fizzy/value.hpp
Outdated
@@ -26,11 +26,10 @@ union Value | |||
/// We need to support {signed,unsigned} x {32,64} integers. However, due to uint64_t being |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment is outdated.
lib/fizzy/value.hpp
Outdated
/// Some issues are expected when uint64_t is not unsigned long. | ||
/// Then Value cannot be constructed out of unsigned long literals. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"some issues" sounds a bit confusing to me, maybe this:
/// Some issues are expected when uint64_t is not unsigned long. | |
/// Then Value cannot be constructed out of unsigned long literals. | |
/// On the platforms where uint64_t is not unsigned long, it is expected that | |
/// Value cannot be constructed out of unsigned long literals. |
This disables Value constructors for unsigned integers for types other than uint32_t/uint64_t. This requires users to use these types. This can cause portability issues on macOS/Linux if type like unsigned long is used. This also helps in 32-bit port.
This disables Value constructors for unsigned integers for types other
than uint32_t/uint64_t. This requires users to use these types.
This can cause portability issues on macOS/Linux if type like
unsigned long is used. This also helps in 32-bit port.