News for hackers. Stuff that matters.

A comment on The Rust standard library no longer has any scheduling baked into it. Parent comment

Re:The Rust standard library no longer has any scheduling ba... by qznc on Sunday December 29, 2013 @05:40AM (#6979136)
C integration is the killer for N:M threading. C libraries do blocking IO, are not wrapped into a VM, are not compiled for segmented stacks, use thread-local storage, etc. You can work around this problems, which increases complexity. For close C integration, you are basically forced to adopt Cs view of threading.
[ Parent | on HN ]
Re:The Rust standard library no longer has any scheduling ba... by jlouis on Sunday December 29, 2013 @01:01PM (#6980467)
This is why the R17 release of Erlang might get "dirty schedulers" for this kind of work. Essentially it gives you background thread pools where such work can be carried out.

Currently, you can call C functions directly, but it is not meant for long-running tasks which can block and so on.

[ Parent | on HN ]
Re:The Rust standard library no longer has any scheduling ba... by wcummings on Sunday December 29, 2013 @06:48PM (#6982162)
If E17 includes this AND maps I might cry (':
[ Parent | on HN ]