On 06/01/2013 12:08 AM, Vadim wrote:
On Fri, May 31, 2013 at 3:45 PM, Brian Anderson bander...@mozilla.com
mailto:bander...@mozilla.com wrote:
With this problem in general I think the obvious solutions amount
to taking one of two approaches: translate I/O events into pipe
On 06/01/2013 11:49 PM, Matthieu Monrocq wrote:
On Sat, Jun 1, 2013 at 8:35 PM, Vadim vadi...@gmail.com
mailto:vadi...@gmail.com wrote:
On Sat, Jun 1, 2013 at 7:47 AM, Matthieu Monrocq
matthieu.monr...@gmail.com mailto:matthieu.monr...@gmail.com
wrote:
1.
On 06/02/2013 03:44 PM, Brian Anderson wrote:
On 06/01/2013 11:49 PM, Matthieu Monrocq wrote:
On Sat, Jun 1, 2013 at 8:35 PM, Vadim vadi...@gmail.com
mailto:vadi...@gmail.com wrote:
On Sat, Jun 1, 2013 at 7:47 AM, Matthieu Monrocq
matthieu.monr...@gmail.com
On Fri, May 31, 2013 at 3:45 PM, Brian Anderson bander...@mozilla.comwrote:
With this problem in general I think the obvious solutions amount to
taking one of two approaches: translate I/O events into pipe events;
translate pipe events into I/O events. Solving the problem efficiently for
I know that Rust currently doesn't currently support this, but what if
futures could use a custom allocator? Then it could work like this:
1. Futures use a custom free-list allocator for performance.
2. The I/O request allocates new future object, registers uv event, then
returns unique
On Sat, Jun 1, 2013 at 3:43 PM, Thad Guidry thadgui...@gmail.com wrote:
I know that Rust currently doesn't currently support this, but what if
futures could use a custom allocator? Then it could work like this:
1. Futures use a custom free-list allocator for performance.
I don't see why
On Sat, Jun 1, 2013 at 7:47 AM, Matthieu Monrocq matthieu.monr...@gmail.com
wrote:
1. Futures use a custom free-list allocator for performance.
I don't see why Futures could not be allocated on the stack ?
Since Rust is move aware and has value types, it seems to me this should
be
## Design and implement some solution for select / async events
We need a way to efficiently wait on multiple types of events at once,
including port receives, I/O reads, socket accepts, timers. This has some
very complicated requirements to satisfy, as detailed in the linked issue,
and I'm
## Design and implement some solution for select / async events
We need a way to efficiently wait on multiple types of events at once,
including port receives, I/O reads, socket accepts, timers. This has some
very complicated requirements to satisfy, as detailed in the linked issue,
and I'm
On 05/31/2013 10:18 AM, Vadim wrote:
## Design and implement some solution for select / async events
We need a way to efficiently wait on multiple types of events at
once, including port receives, I/O reads, socket accepts, timers.
This has some very complicated requirements to
On 05/31/2013 01:14 PM, Thad Guidry wrote:
## Design and implement some solution for select / async events
We need a way to efficiently wait on multiple types of events at
once, including port receives, I/O reads, socket accepts, timers.
This has some very complicated
Hi Rusties,
Allow me to present the status of our ongoing quest to rewrite the task
scheduler, along with the major work items remaining. The results so far
are encouraging but there is a very large amount of work left,
particularly regarding I/O. In addition to myself we'll have two interns
12 matches
Mail list logo
