We need an efficient mechanism/error class for seamlessly handling WSAE* results from windows socket api calls without an excessive switch case block of all possible translations. This may look like a new error class, mapped to a single int (DWORD) errno_ member, which can be evaluated with isEAgain(), isENotFound() and similar methods of evaluation.

This is a tracking issue just to note that @sunjayBhatia and I are attacking this puzzle next, during the first week of June. We expect this single change will eliminate a significant percentage of currently-failing tests on windows.

tag: area/windows