https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try 2024-01-11T19:10:25+00:00 2024-01-11T19:10:25+00:00 joboet jonasboettiger@icloud.com 2024-01-11T19:10:25+00:00 urn:sha1:99128b7e45f8b95d962da2e6ea584767f0c85455 2023-10-24T11:14:15+00:00 bors bors@rust-lang.org 2023-10-24T11:14:15+00:00 urn:sha1:cee6db171d03c22f1cbf98a72dffde858a49fbd8 Windows: Support sub-millisecond sleep Use `CreateWaitableTimerExW` with `CREATE_WAITABLE_TIMER_HIGH_RESOLUTION`. Does not work before Windows 10, version 1803 so in that case we fallback to using `Sleep`. I've created a `WaitableTimer` type so it can one day be adapted to also support waiting to an absolute time (which has been talked about). Note though that it currently returns `Err(())` because we can't do anything with the errors other than fallback to the old `Sleep`. Feel free to tell me to do errors properly. It just didn't seem worth constructing an `io::Error` if we're never going to surface it to the user. And it *should* all be infallible anyway unless the OS is too old to support it. Closes #43376 2023-10-06T05:06:43+00:00 Chris Denton chris@chrisdenton.dev 2023-10-05T22:54:33+00:00 urn:sha1:fca182b6a0c43f3240d6c76397cad1c143e3774c Use `CreateWaitableTimerExW` with `CREATE_WAITABLE_TIMER_HIGH_RESOLUTION`. Does not work before Windows 10, version 1803 so in that case we fallback to using `Sleep`. 2023-10-05T23:35:00+00:00 Chris Denton chris@chrisdenton.dev 2023-10-05T23:35:00+00:00 urn:sha1:c8f3aa451a0b50051980cf22d5ca35d7f515b43b We don't use much libc on Windows. 2023-05-05T19:48:16+00:00 Chris Denton chris@chrisdenton.dev 2023-04-06T16:27:47+00:00 urn:sha1:3ffb27ff89db780e88abe829783565a7122be1c5 2023-01-17T13:08:35+00:00 joboet jonasboettiger@icloud.com 2023-01-17T13:08:35+00:00 urn:sha1:7f2cf191917e4e562ee49ab51a324714bbb36412 2023-01-14T16:22:04+00:00 André Vennberg andre.vennberg@gmail.com 2023-01-14T15:33:11+00:00 urn:sha1:0b35f448f8e9f39ed6fc1c494eeb331afba513bc 2022-05-09T09:12:32+00:00 Mara Bos m-ou.se@m-ou.se 2022-05-09T09:12:32+00:00 urn:sha1:4f212f08cf0edb1fe990c8ca30fef09c27606682 2022-03-04T21:58:37+00:00 Dylan DPC 99973273+Dylan-DPC@users.noreply.github.com 2022-03-04T21:58:37+00:00 urn:sha1:629e7aa71803ea3300559e65a4abc17dba984837 Don't round stack size up for created threads in Windows Fixes #94454 Windows does the rounding itself, so there isn't a need to explicity do the rounding beforehand, as mentioned by ```@ChrisDenton``` in #94454 > The operating system rounds up the specified size to the nearest multiple of the system's allocation granularity (typically 64 KB). To retrieve the allocation granularity of the current system, use the [GetSystemInfo](https://docs.microsoft.com/en-us/windows/win32/api/sysinfoapi/nf-sysinfoapi-getsysteminfo) function. https://docs.microsoft.com/en-us/windows/win32/procthread/thread-stack-size 2022-03-04T18:04:43+00:00 Lewis Clark me@lewis.to 2022-03-04T18:04:43+00:00 urn:sha1:6843dd5013545652ccd1ff3e63462d6cffbe1dcf