-
-
Notifications
You must be signed in to change notification settings - Fork 16.1k
Tracking Issue for VaArgSafe in bounds (c_variadic_va_arg_safe) #162911
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-design-concernsStatus: There are blocking design concerns.Status: There are blocking design concerns.T-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.
Description
Activity
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-design-concernsStatus: There are blocking design concerns.Status: There are blocking design concerns.T-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.
Feature gate:
#![feature(c_variadic_va_arg_safe)]This is a tracking issue for the
VaArgSafetrait (part of rust-lang/rfcs#2137).See also the tracking issue for
c_variadic, where the API of this feature was intially stabilized on beta: #44930Zulip stream: #t-libs > Implementing `VaArgSafe` on references is a breaking change
Public API
Steps / History
VaArgSafe#162909Unresolved Questions
Footnotes
https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩