Hi Brian,
On Sat, Nov 15, 2014 at 11:23 PM, Brian Anderson wrote:
> I believe it is not possible to link to glibc statically. My understanding
> is that to get a Rust binary that does not depend on a system-provided libc
> at all we need to add explicit support for alternate libc
> implementation
Hi Kai,
On Sat, Nov 15, 2014 at 11:02 PM, Kai Noda wrote:
> Hi Paul,
>
> I managed to get it working by manually tweaking linker options (this
> mustn't be the right way to go...)
>
> Rust devs: what is the official way to do this? Simply adding "-C
> link-args=-static" doesn't work (see my seco
Hi,
Is there any way to compile static binary with rust compiler? I'm
experimenting with linux conainerisation and it would be much easier
if I could compile a binary which doesn't depend on libc.
There is also an stack overflow question with no answer:
http://stackoverflow.com/questions/26202494
Hi Michael,
On Mon, Oct 13, 2014 at 8:41 AM, Michael Giagnocavo wrote:
> I came across the "if let" syntax, and it's been bothering me a bit.
>
> It seems like a strange thing to elevate to a grammar-level construct.
>
> The example given is:
> if let Some(x) = foo() {
> doSomethingWith(x)
>
Hi,
On Mon, Sep 29, 2014 at 11:01 PM, Wink Saville wrote:
> Nanomsg looks interesting and I'll take a closer look. But I'm interested in
> a pure rust implementation of async messaging because I'd like to create an
> embedded OS using rust and not use C if possible.
>
I think even if there will
Hi Alex,
Sorry for replying off-list, previously. I would try to argue on the
both points:
On Fri, May 16, 2014 at 2:09 AM, Alex Crichton wrote:
>>> There is no way to generically wake up or kill a task, it must be
>>> arranged via some other means for the task to wake up.
>>
>> Is this intentio
Hi,
I have a few kinds of tasks like the ones reading from a TCP socket or
listening for TCP connections, that need to be shut down when
unneeded. How can I wake up/kill a task waiting for data in
Reader.read() method or similar?
In the master branch I can set_timeout and wake up once a while (wh
Hi,
On Tue, Oct 1, 2013 at 9:13 AM, Oren Ben-Kiki wrote:
> I know, this is pretty horrible... what is the "right thing" here? Using
> {:s} and keep calling .to_str() everywhere?
>
Not sure if that helps. But in python there are conversion specifiers
"{!s}" and "{!r}" which convert to string expl
