-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Labels
B2 - improvementBucket 2 as described by P0592: bug fixes, performance improvements, integration fixes for/between eBucket 2 as described by P0592: bug fixes, performance improvements, integration fixes for/between eC++29Targeted at C++29Targeted at C++29EWGEvolutionEvolutionISShip vehicle: ISShip vehicle: ISLEWGLibrary EvolutionLibrary EvolutionLEWGILibrary Evolution IncubatorLibrary Evolution IncubatorSG6NumericsNumericsneeds-revisionPaper needs changes before it can proceedPaper needs changes before it can proceedsize - largepaper size estimatepaper size estimate
Description
P3140R0 std::int_least128_t (Jan Schultke)
stephenberry
Metadata
Metadata
Assignees
Labels
B2 - improvementBucket 2 as described by P0592: bug fixes, performance improvements, integration fixes for/between eBucket 2 as described by P0592: bug fixes, performance improvements, integration fixes for/between eC++29Targeted at C++29Targeted at C++29EWGEvolutionEvolutionISShip vehicle: ISShip vehicle: ISLEWGLibrary EvolutionLibrary EvolutionLEWGILibrary Evolution IncubatorLibrary Evolution IncubatorSG6NumericsNumericsneeds-revisionPaper needs changes before it can proceedPaper needs changes before it can proceedsize - largepaper size estimatepaper size estimate
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
erichkeane commentedon Mar 21, 2024
EWGI discussed this in Tokyo during the Thursday AM session. The following poll was taken:
EWGI believes P3140R0 is sufficiently well developed, EWGI forwards it to EWG.
Result: Consensus
ALSO forwarding to SG22 and SG6 for the chairs to decide whether this should be seen there as well.
jfbastien commentedon Jun 27, 2024
Seen in EWG in St Louis:
Poll: P3140R0 — std::int_least128_t, we are interested in adding some form of an int128 type in C++ and encourage further work.
| SF | F | N | A | SA |
| 9 | 12 | 3 | 2 | 0 |
i128
/u128
from theimproper_ctypes
lint rust-lang/lang-team#255NinaRanns commentedon Sep 10, 2024
Seen on 28/08/2024
No concerns regarding compatibility. Concern raised about making types mandatory for freestanding. Feedback given to the author. WG14 would be interested in a WG14 version of the paper.
Minutes from SG22 discussion
eisenwave commentedon Jun 24, 2025
I'm stepping away from this proposal.
The implementation investigation and motivation are very valuable, and the feedback from St. Louis was very helpful, but I am under the impression now that this problem is worth solving more generally in the form of bringing
_BitInt
to C++29. This will be done under paper number P3666.jensmaurer commentedon Jun 24, 2025
Closing since author lost interest.