From andrew@egeler.us

<retupmoca> jnthn​: is it known that "await start { .say for lines }" breaks on windows console (with perl6-m)?
<retupmoca> jnthn​: or should I rakudobug?
<J-L> On my Windows, perl6-m -e "await start { .say for lines }" gives me​: ===SORRY!=== and I have to CTRL-C to get out.
<jnthn> retupmoca​: Wasn't known to me, but I can reproduce it

Expected result​: Same behavior as “.say for lines” (without threading)

From @smls

On Linux, I don't get that "expected result" either.

It does not print an error, but simply does nothing, i.e.
- doesn't echo STDIN lines
- doesn't quit when STDIN is closed with [ctrl]+d

Simple ".say for lines" without the "await start { }" does both of those things.

The RT System itself - Status changed from 'new' to 'open'

From @nwc10

MoarVM work towards fixing this bug is on the MoarVM branch sync-without-uv

From @jnthn

On Fri Nov 20 10​:21​:26 2015, nicholas wrote​:

MoarVM work towards fixing this bug is on the MoarVM branch sync-without-uv

Having already ran into various "fun" platform inconsistencies working on that branch, I've concluded that - while I agree this issue wants fixing - it's not something that it's sensible to try and sneak in this side of the Christmas release, since it risks destabilizing a bunch of things that work fine, for the sake of a more rare thing that does not. So, it's off the xmas tickets list. It's pretty much certain that nobody will write code that relies on this failing to work, so fixing it after xmas and making it something you can expect to work in 6.d (and so including it in the test suite then) will be fine.

Note that while this ticket doesn't mention it, the issue also exists for synchronous sockets; there, though, there's an easy workaround, which is to use IO​::Socket​::Async, so it's even less of an issue.

From @zoffixznet

Tests appear to exist in t/spec/S16-io/handles-between-threads.t

From @jnthn

On Fri, 19 Aug 2016 12​:04​:15 -0700, cpan@​zoffix.com wrote​:

Tests appear to exist in t/spec/S16-io/handles-between-threads.t

And have been fully passing since earlier this year when the issue of handles between threads was addressed; resolving.

@jnthn - Status changed from 'open' to 'resolved'