Hi,
I'm trying to interface to some C code which uses a lot of structs. I
can declare these using raw pointers, but then I lose the benefits of
Rust's compile-time pointer checking. So I tried replacing the raw
pointers with owned pointers, which more accurately captures the
meaning of the C
On Sat, 2013-05-25 at 11:09 +0100, Thomas Leonard wrote:
Hi,
Hi!
I'm trying to interface to some C code which uses a lot of structs. I
can declare these using raw pointers, but then I lose the benefits of
Rust's compile-time pointer checking. So I tried replacing the raw
pointers with owned
On 25 May 2013 12:03, Benjamin Herr b...@0x539.de wrote:
On Sat, 2013-05-25 at 11:09 +0100, Thomas Leonard wrote:
Hi,
Hi!
I'm trying to interface to some C code which uses a lot of structs. I
can declare these using raw pointers, but then I lose the benefits of
Rust's compile-time pointer
In cases like this the normal thing to do is to make the C structures
private and expose an abstract interface. Check out my zeromq binding, it
might be helpful:
https://github.com/erickt/rust-zmq/blob/master/zmq.rc
In your case with xmlParseFile, I would suggest not returning a pointer at
all,
On 10/05/13 01:45, Graydon Hoare wrote:
On 13-05-07 08:09 AM, Sanghyeon Seo wrote:
Here are some feature requests to bors queue status page at
http://buildbot.rust-lang.org/bors/bors.html
3. OUTDATED state, for pull requests that need to be rebased. GitHub
API provides mergeable attribute for
On Sat, May 25, 2013 at 2:36 PM, Gareth Smith
garethdanielsm...@gmail.com wrote:
I am guessing that STALE on http://buildbot.rust-lang.org/bors/bors.html
means needs rebase - right?
Yes
How does a pull request leave the STALE state? Does it have to be reviewed
again or will the status
Hi rust-dev,
I thought we should have a brief discussion on the development policy,
specifically about bug assignment (from the perspective of a new
contributor to the Rust codebase).
# Motivation
I had a working patch for fixing a small Rust issue (my first Rust
bug) at one point before some
I agree that this is a real concern. It may not be happening very
often so far, but it's a seriously bad feeling to find that someone
else has gone ahead and done the same work you were making headway on
(regardless of intent).
I think if it's possible on github, we should have a way for any
