-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
Tracking Issue for TIMESPEC_MAX_CAPPED on QNX Neutrino #108597
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 RFCO-neutrinoOS: QNX Neutrino, a POSIX-compatible real-time operating systemOS: QNX Neutrino, a POSIX-compatible real-time operating systemT-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.
Description
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 RFCO-neutrinoOS: QNX Neutrino, a POSIX-compatible real-time operating systemOS: QNX Neutrino, a POSIX-compatible real-time operating systemT-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.
Review finding of #106673 (adding QNX Neutrino support to the standard library):
TIMESPEC_MAX_CAPPEDis introduced additionally toTIMESPEC_MAX. Both are only visible inside the standard library but onlyTIMESPEC_MAX_CAPPEDis used. It would make sense to consolidate them.cc: @gh-tr
@rustbot label +O-neutrino