Hi,
Yesterday mozilla's staff rust developers agreed to alter the git
workflow for the mozilla/rust repository, to help ensure master always
remains green (and cut down on the amount of anxious tree-watching and
panicked scrambles to unblock others).
Until further notice, the policy is
Hello,
I wanted to check something. We are working on the Great Change to a
more flexible vector system and I want to outline the design that's in
my head. This has some implications for How Efficient Rust Code Is
Written, so I wanted to make sure we were all on the same page.
*Implications
On 06/13/2012 04:15 PM, Niko Matsakis wrote:
Hello,
I wanted to check something. We are working on the Great Change to a
more flexible vector system and I want to outline the design that's in
my head. This has some implications for How Efficient Rust Code Is
Written, so I wanted to make sure we
On 6/13/12 4:31 PM, Brian Anderson wrote:
This method of creating vectors originally had worse performance than
the other. Is the performance problem resolved or resolvable or is
vector creation just going to be expensive?
This would of course get resolved.
Actually, I don't think building
On 6/12/12 3:33 PM, Graydon Hoare wrote:
Try sketching some code in a buffer, see how it looks. Might be
possible to come up with an abbreviation (!T perhaps, or the old
unused sigil ?T maybe?), might be possible for inference and a couple
rules about the boundaries of extern functions to fill
On 6/13/12 6:37 PM, Niko Matsakis wrote:
On 6/12/12 3:33 PM, Graydon Hoare wrote:
Try sketching some code in a buffer, see how it looks. Might be
possible to come up with an abbreviation (!T perhaps, or the old
unused sigil ?T maybe?), might be possible for inference and a couple
rules about
