about summary refs log tree commit diff
path: root/src/rt/rust_run_program.cpp
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2013-03-25 13:01:11 -0700
committerbors <bors@rust-lang.org>2013-03-25 13:01:11 -0700
commitef282dbe2af9c6afc89776df177a750a1784853a (patch)
tree61c5a5f9b4c16d8b1d06a5dc3eaa68052a119cbf /src/rt/rust_run_program.cpp
parent6d4499ce4d948bf7b7b385b40e5b3536507ad3e8 (diff)
parent30d4124a374489de1776eb1b8076ca533041fa18 (diff)
downloadrust-ef282dbe2af9c6afc89776df177a750a1784853a.tar.gz
rust-ef282dbe2af9c6afc89776df177a750a1784853a.zip
auto merge of #5409 : brson/rust/rt, r=brson
r?

There are a lot of commits here, but not all that much substance. Mostly just refactoring.

I started sketching out the beginnings of a very simple I/O API in `core::rt::io` that represents I/O streams as a single `Stream` trait instead of `Reader` / `Writer` pairs. This seems to be the more common pattern (at least this is how the .NET BCL does it) and it seems to me that separate readers and writers would make duplex streams very awkward. Regardless, I don't intend to go very far down the I/O API design road without some mailing list discussion.

I've also started on the uv bindings for file I/O but haven't gotten very far.

Also hooked up the new scheduler to `rust_start` and the compiletest driver. 70% of run-pass test cases already pass, but I wouldn't read too much into that.

I also split the direct, low-level uv bindings in two so that the scheduler can have its own set, leaving `std::net` on its own.
Diffstat (limited to 'src/rt/rust_run_program.cpp')
0 files changed, 0 insertions, 0 deletions