receiveOnly behavior

[Sean Kelly]

On May 4, 2011, at 2:05 PM, jdrewsen wrote:

> import std.concurrency;
> 
> void main(string[] args) {
>  receiveOnly!bool();
> }
> 
> This simple program results in segmentation fault. I know i does not spawn a thread to receive anything from but is this the expected behavior?

This was a known issue when calling receive() in the main thread before ever calling thisTid().  Doing so seemed rather unlikely, but fixing this was a trivial code change so I've just done so.  Expect your sample to not segfault in the next release.