On Sat Jan 25 05:37:01 2025 +0000, William Horvath wrote:
I mean, before this, we were returning a completely unexpected result for `NtDelayExecution` (`STATUS_TIMEOUT`). If, by your suggestion, we instead always return `STATUS_SUCCESS` for alertable waits, that'd be almost the complete inverse of what Windows returns (for 1ms resolution). If an application happened to care about the return value of the delay, I feel like the current version is more likely to be correct than if we basically flipped the NO_YIELD/SUCCESS ratio from ~100%/~0% to 0%/100%.
Why this statistics matters in practice? For non-alertable 0ms waits it won’t yield most of the time and return the corresponding status. For each 0ms alertable wait it *does yield 100% of the time*, do you have any practical reason to lie about that in return status, any app behaves better this way for some explained reason?