On 11-04-15 12:04 PM, David Herman wrote:
I don't have any concrete solutions to offer, just a few scattered
thoughts:
- In our recent discussions at the all-hands, we were leaning towards
eliminating the ability to send higher-order data over channels. This
would be in tension with the desire to migrate tasks.
This would make it easier to migrate tasks, no?
- Migrating tasks could be done in a more expressive way if we had
continuations: you could suspend your entire task. (This may just be
an equivalent way of looking at task migration. But actually
continuations can be a good fit for lower-level languages like Rust,
independent of the use case of migration: they are helpful for
building systems like OSes and web servers. I'm not advocating, just
putting this out there.)
Well, we have basic continuations: the stack :-)
A language that makes call-cc cheap would make task migration cheap, but
is there a way to do it without putting the majority of the data in a
common GCed heap (a la smlnj)?
Dave
Cheers,
Rafael
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev
