On Sat, May 3, 2014 at 2:27 AM, Artella Coding
artella.cod...@googlemail.com wrote:
Hi looking at https://github.com/rust-lang/rfcs/pull/59 , is it the case
that the following replacement rules apply :
1) ~T is replaced by BoxT
2) ~[T] is replaced by VecT
and what does little box (as
That will be possible, but the Index trait needs to be overhauled first.
Steven Fackler
On Sun, May 4, 2014 at 3:01 PM, Brian Rogoff brog...@gmail.com wrote:
On Sat, May 3, 2014 at 2:27 AM, Artella Coding
artella.cod...@googlemail.com wrote:
Hi looking at
Fair enough, but I hope that the Index trait overhaul is merged before the
ability to use slices like this is removed. To do otherwise would be
unpleasant.
On Sun, May 4, 2014 at 3:09 PM, Steven Fackler sfack...@gmail.com wrote:
That will be possible, but the Index trait needs to be overhauled
On 04/05/14 07:03 PM, Brian Rogoff wrote:
Fair enough, but I hope that the Index trait overhaul is merged before
the ability to use slices like this is removed. To do otherwise would be
unpleasant.
The ability to grow ~[T] was already removed, and it would be really
nice to remove the
Right, I don't need these matrices to grow, I know their permanent sizes
when I create them, and I used to use slices::from_elem but that went away
a few days ago. I always assumed that ~[T] was more like a builtin, fixed
size, array, and Vec a growable vector.
I imagine that this will all get
Hi looking at https://github.com/rust-lang/rfcs/pull/59 , is it the case
that the following replacement rules apply :
1) ~T is replaced by BoxT
2) ~[T] is replaced by VecT
and what does little box (as opposed to BoxT) do?
When will these changes appear in the nightlies? I am using rustc
Yes, yes, and
let x = box 5;
let x = ~5;
same thing. It's also more general:
let x = box(GC) 5;
and lets all of these pointers support placement new, which only ~ did
previously:
fn foo() - int { ...
let x = box foo();
Now that the RFC has been accepted, patches can be
On 3 May 2014 12:12, Steve Klabnik st...@steveklabnik.com wrote:
It's also more general:
let x = box(GC) 5;
Would x here have a copy semantic like plain numbers or would it still
use move as box(Heap) 5 will?
___
Rust-dev mailing list
