-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Tracking Issue for const stability of unsigned bigint helpers #152015
Copy link
Copy link
Open
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-unimplementedStatus: The feature has not been implemented.Status: The feature has not been implemented.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Metadata
Metadata
Assignees
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-unimplementedStatus: The feature has not been implemented.Status: The feature has not been implemented.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Feature gate:
#This is a tracking issue for the const stability of the bigint helper methods added in 1.91.0.
Public API
Steps / History
(Remember to update the
S-tracking-*label when checking boxes.)bigint_helper_methods#144494Notes
These were originally not stabilised as part of the original per @scottmcm:
Note that at minimum, a T-lang FCP would be needed on a stabilization PR to accept the const-stabilization of those intrinsics. Additionally, we will probably be blocked on
#[const_trait]being stable unless there's a blessing from at least a few folks involved to stabilize these methods regardless.Unresolved Questions