Add overloads for WaitHandle.Wait(Any/All) with ReadOnlySpan<WaitHandle>

[hrrrrustic]

Background and Motivation

Since calls from all overloads of those methods comes to this private method which takes ReadOnlySpan, it may be useful to add public overloads with ReadOnlySpans (for example to use with stackalloc)

Proposed API

public static bool WaitAll(ReadOnlySpan<WaitHandle> waitHandles, int millisecondsTimeout);
public static bool WaitAll(ReadOnlySpan<WaitHandle> waitHandles, TimeSpan timeout);
public static bool WaitAll(ReadOnlySpan<WaitHandle> waitHandles);
public static bool WaitAll(ReadOnlySpan<WaitHandle> waitHandles, int millisecondsTimeout, bool exitContext);
public static bool WaitAll(ReadOnlySpan<WaitHandle> waitHandles, TimeSpan timeout, bool exitContext);

public static int WaitAny(ReadOnlySpan<WaitHandle> waitHandles, int millisecondsTimeout);
public static int WaitAny(ReadOnlySpan<WaitHandle> waitHandles, TimeSpan timeout);
public static int WaitAny(ReadOnlySpan<WaitHandle> waitHandles);
public static int WaitAny(ReadOnlySpan<WaitHandle> waitHandles, int millisecondsTimeout, bool exitContext);
public static int WaitAny(ReadOnlySpan<WaitHandle> waitHandles, TimeSpan timeout, bool exitContext);

[svick]

• Are the overloads taking int timeout necessary?
• Could the number of overloads be decreased by using optional parameters?

[hrrrrustic]

• No, I don't think so. As I see here, TimeSpan version is more prior. Just copied overloads from existing ones :)
• Yeah, it would be great, but it seems like it's possible only for int overloads. Timeout default value is -1 everywhere, but we can't use TimeSpan as constant for optional parameter.

So, we will get 6 proposed overloads in case of removing int overloads, and 8 overloads in case of using optional parameters for int timeout, but it's also possible to reduce existing overloads number this way safely

Btw have no idea about bool exitContext argument and its usage

[dotnet-policy-service]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.