Make fixed_bit_length a primary template [SyncWith: marshalling#32] #32
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
x-mass
changed the title
|
PRs, synced with the current issue:
Note: Please do not edit this comment; it's generated automatically. |
x-mass
force-pushed
the
bitfield_extension
branch
from
cf09176
to
51f2f80
Compare
|
Tests will be run in sync with other PRs containing |
x-mass
force-pushed
the
bitfield_extension
branch
from
51f2f80
to
76a66a6
Compare
x-mass
force-pushed
the
bitfield_extension
branch
from
6ecb98f
to
4a000ab
Compare
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.
We need to make fixed_bit_length a primary template to have an ability to create specialization for it, so we could use other underlying types as well. Espesially now it is needed for using mulriprecision integers as bitfield members