Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upTracking issue for some Duration-taking functions #27771
Comments
alexcrichton
added
T-libs
B-unstable
E-easy
labels
Aug 12, 2015
alexcrichton
added
the
final-comment-period
label
Aug 14, 2015
This comment has been minimized.
This comment has been minimized.
|
This feature is now entering its final comment period for stabilization. |
This comment has been minimized.
This comment has been minimized.
|
What do we do with the |
nagisa
referenced this issue
Sep 2, 2015
Closed
milliseconds should be represented by u64, not u32 type #28171
This comment has been minimized.
This comment has been minimized.
|
Yeah we'd just deprecate them all in place |
This comment has been minimized.
This comment has been minimized.
|
Before we deprecate something |
This comment has been minimized.
This comment has been minimized.
|
@SimonSapin We've talked about tying deprecation to particular versions, so that the warnings don't start until the relevant stable release (but it still shows as deprecated in rustdoc, etc). For the time being, we can just do this manually by waiting to deprecate. |
This comment has been minimized.
This comment has been minimized.
|
@aturon Yes, either of these would work. |
alexcrichton commentedAug 12, 2015
This is a tracking issue for some small Duration-taking functions in the standard library, specifically the
park_timeoutandthread_sleepfunctions. Now thatDurationis stabilized these are likely ready to be stable as-is.