• sanjayss (4/4) Feb 03 2016 Are the functions lastSocketError() and wouldHaveBlocked() from
• tcak (12/16) Feb 04 2016 Not directly read the code for a while (but did before), those

sanjayss <dummy dummy.dummy> writes:

Are the functions lastSocketError() and wouldHaveBlocked() from 
std.socket thread-safe? i.e. can they be reliably used to see the 
status of the last socket call when sockets are being 
read/written in multiple threads?

tcak <1ltkrs+3wyh1ow7kzn1k sharklasers.com> writes:

On Thursday, 4 February 2016 at 06:40:15 UTC, sanjayss wrote:
 Are the functions lastSocketError() and wouldHaveBlocked() from 
 std.socket thread-safe? i.e. can they be reliably used to see 
 the status of the last socket call when sockets are being 
 read/written in multiple threads?

Not directly read the code for a while (but did before), those 
two functions
call C functions, and they are thread-safe by default. The 
WOULD-HAVE-BLOCKED
is understood by checking errno which comes from core.stdc.errno. 
If you read
that function's documents, you will see that it is marked as 
thread-safe.

http://linux.die.net/man/3/errno
... errno is thread-local; setting it in one thread does not 
affect its value in any other thread. ...