diff options
| author | bors <bors@rust-lang.org> | 2013-11-25 05:46:37 -0800 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2013-11-25 05:46:37 -0800 |
| commit | fffacb34fec23da45c4d18ce8504c7947527aa78 (patch) | |
| tree | a59470563bc3b39b3d32f16ea5fb235c0a1d48e6 /src/rustllvm/RustWrapper.cpp | |
| parent | 1746c0269d356a93aaef367541872d363651cb23 (diff) | |
| parent | 6acf227cc8db09ca25d274918f860849c41df19a (diff) | |
| download | rust-fffacb34fec23da45c4d18ce8504c7947527aa78.tar.gz rust-fffacb34fec23da45c4d18ce8504c7947527aa78.zip | |
auto merge of #10646 : alexcrichton/rust/issue-10645, r=luqmana
This is a behavioral difference in libuv between different platforms in different situations. It turns out that libuv on windows will immediately allocate a buffer instead of waiting for data to be ready. What this implies is that we must have our custom data set on the handle before we call uv_read_start. I wish I knew of a way to test this, but this relies to being on the windows platform *and* reading from a true TTY handle which only happens when this is actually attached to a terminal. I have manually verified this works. Closes #10645
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
