News for hackers. Stuff that matters.

A comment on Rust 0.10 released. Parent comment

Re:Rust 0.10 released by dbaupp on Thursday April 03, 2014 @08:51PM (#7528367)
I don't think #[no_std] has any effect here, other that guaranteeing that know runtime-using functions are called (by not linking in any runtime at all).

I believe you can also just start runtimes in each call into Rust. Obviously it won't be particularly efficient.

[ Parent | on HN ]
Re:Rust 0.10 released by ben0x539 on Thursday April 03, 2014 @09:42PM (#7528565)
That's what I meant re: no_std, yeah.

Would it be possible to lazily start libnative if a call into the runtime is made but there's none there, but then keep it running for that thread for subsequent calls?

[ Parent | on HN ]
Re:Rust 0.10 released by dbaupp on Friday April 04, 2014 @06:48AM (#7530441)
Maybe? The current design is starting a runtime is a blocking call, though, i.e. I think you'd call `native::run`[1] and run anything needing a runtime inside that (I haven't experimented with this part of our FFI in detail).

[1]: http://static.rust-lang.org/doc/master/native/fn.run.html

[ Parent | on HN ]