diff options
| author | bors <bors@rust-lang.org> | 2023-10-24 11:14:15 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-10-24 11:14:15 +0000 |
| commit | cee6db171d03c22f1cbf98a72dffde858a49fbd8 (patch) | |
| tree | b5d2cf4db7a77f41a5b4f7edf6337241ce600cd7 /tests/ui/async-await/in-trait/async-generics.rs | |
| parent | 271dcc1d40b57ad129d88fef1aa7f239308fbfb4 (diff) | |
| parent | fbf256716e499d9b2ee15c722c63d90d960f2859 (diff) | |
| download | rust-cee6db171d03c22f1cbf98a72dffde858a49fbd8.tar.gz rust-cee6db171d03c22f1cbf98a72dffde858a49fbd8.zip | |
Auto merge of #116461 - ChrisDenton:sleep, r=thomcc
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
Diffstat (limited to 'tests/ui/async-await/in-trait/async-generics.rs')
0 files changed, 0 insertions, 0 deletions