You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the runtime package, on Windows, if the function GetQueuedCompletionStatusEx is not available on the system, we use the simpler but slower GetQueuedCompletionStatus function.
Therefore, I believe that all supported Windows systems support GetQueuedCompletionStatusEx, and we can remove the code that uses GetQueuedCompletionStatus.
In the runtime package, on Windows, if the function
GetQueuedCompletionStatusEx
is not available on the system, we use the simpler but slowerGetQueuedCompletionStatus
function.According to https://docs.microsoft.com/en-us/windows/win32/fileio/getqueuedcompletionstatusex-func,
GetQueuedCompletionStatusEx
is available on Windows Vista, Windows Server 2008, and newer.According to https://golang.org/wiki/MinimumRequirements, as of the Go 1.11 release we require at least Windows 7, or Windows 2008R2, or higher.
According to https://en.wikipedia.org/wiki/List_of_Microsoft_Windows_versions, Windows 7 is newer than Windows Vista.
Therefore, I believe that all supported Windows systems support
GetQueuedCompletionStatusEx
, and we can remove the code that usesGetQueuedCompletionStatus
.@alexbrainman @mattn Do you agree?
The text was updated successfully, but these errors were encountered: