So at some future point it would be possible to replace
TypedArena_instance().alloc(X) with box(TypedArena_instance) X
avoiding an extra move of X from a temporary allocated on the stack
that the compiler in general cannot optimize?
On 3 July 2014 04:39, Corey Richardson co...@octayn.net wrote:
On 7/2/14 11:08 PM, Igor Bukanov wrote:
So at some future point it would be possible to replace
TypedArena_instance().alloc(X) with box(TypedArena_instance) X
avoiding an extra move of X from a temporary allocated on the stack
that the compiler in general cannot optimize?
Yes. Under the hood,
I've been trying to read up on Rust a little bit, and things look really
amazing. Given the focus on 'safety' and the strong link between safety
and integrity related issues, I was intrigued by the following question:
how far would Rust be removed from possibly becoming an object capability
On 7/2/14 11:09 PM, Rob Meijer wrote:
I've been trying to read up on Rust a little bit, and things look really
amazing. Given the focus on 'safety' and the strong link between safety
and integrity related issues, I was intrigued by the following question:
how far would Rust be removed from
Hi, thanks for your quick replies!
I am thinking that maybe one solution could be that the C code calls
an init function that calls native::start and provides a function pointer
that start calls back into C. That way the C main thread will have a rust
runtime in the background, I *think*?.
I
Perhaps relevant: Cap'n Proto's RPC protocol
http://kentonv.github.io/capnproto/rpc.html aims to be a cross-language
distributed-object-capability system, and I have been working on a Rust
implementation https://github.com/dwrensha/capnproto-rust.
On Thu, Jul 3, 2014 at 2:09 AM, Rob Meijer
The links for FAQ and Manifest Format on http://crates.io should be
rearranged to be at the top of the homepage...instead of the bottom, in my
opinion.
On Wed, Jul 2, 2014 at 7:38 AM, Isak Andersson cont...@bitpuffin.com
wrote:
Hi!
Wow I didn't know about the manifest page, I was under the
I am thinking that maybe one solution could be that the C code calls
an init function that calls native::start and provides a function pointer
that start calls back into C. That way the C main thread will have a rust
runtime in the background, I *think*?.
That is correct!
I hope this would
On Wed, Jul 2, 2014 at 8:56 PM, Brian Anderson bander...@mozilla.com
wrote:
On 07/02/2014 11:19 AM, Gábor Lehel wrote:
Thanks, this is a good step, as is delaying taking actions by a day
as proposed in the meeting itself.
If you have any suggestions for how this regular email or the
On Wed, Jul 2, 2014 at 11:05 PM, Nick Cameron li...@ncameron.org wrote:
On Thu, Jul 3, 2014 at 6:19 AM, Gábor Lehel glaebho...@gmail.com wrote:
Thanks, this is a good step, as is delaying taking actions by a day as
proposed in the meeting itself.
If you have any suggestions for how
Hey Fantix, nice job !
By the way, if you really have time to spare...MQTT would also be a nice
to have library...for the embeddable sensor domain guys.
A bit about it here:
http://clockwerx.blogspot.com/2014/06/whats-mqtt-and-how-can-you-use-it.html
--
-Thad
+ThadGuidry
Aright great! I'll give it a try and let you all know if there is issues.
I'll check the link as well, thank you!
Cheers!
Isak Andersson
On Thu, Jul 3, 2014 at 3:58 PM, Alex Crichton a...@crichton.co wrote:
I am thinking that maybe one solution could be that the C code calls
an init
Here are the recommendations for discussion at next weeks meeting. Last
week we didn't have time to cover older RFCs at the general meeting, so
last weeks RFCs are carried over. Also added is RFC 88 for an update. It
was previously discussed and we decided it hadn't reached a conclusion.
As
13 matches
Mail list logo
