Graydon answered this pretty thoroughly, but just to add:
On Thu, Jun 27, 2013 at 2:39 PM, SiegeLord slab...@aim.com wrote:
Scenario 4: Fetching/building without installation
Building without installing:
rustpkg build URI
If you then run `rustpkg install URI` or `rustpkg install --package
Specificity is the cost of non-virtual dispatch. However, if it is
truly undesirable in some cases, we can eventually permit you to
return `~Iteratorint`, once ~-objects work properly.
Niko
On Wed, Jun 26, 2013 at 11:49:07PM +0100, Gareth Smith wrote:
One downside of external iterators is that
On 6/28/13 11:23 AM, Niko Matsakis wrote:
Specificity is the cost of non-virtual dispatch. However, if it is
truly undesirable in some cases, we can eventually permit you to
return `~Iteratorint`, once ~-objects work properly.
They basically do now (in master), no?
Patrick
On Tue, Jun 25, 2013 at 11:44:10PM -0400, Daniel Micay wrote:
Rust doesn't yet have a way to write data-parallel code, but when it does gain
that, containers can just support partitioning themselves into ranges via
`Iterator`. It will work for in-place mutation in parallel too.
I do not follow
Ah, thanks for clearing that up. That makes much more sense now :)
On Jun 28, 2013 10:04 PM, Björn Steinbrink bstei...@gmail.com wrote:
Hi,
On 2013.06.28 13:27:57 +0200, Michael Woerister wrote:
I hope this question is not too specific for the mailing list, but I
stumbled upon something I
On 13-06-28 11:23 AM, Niko Matsakis wrote:
Specificity is the cost of non-virtual dispatch. However, if it is
truly undesirable in some cases, we can eventually permit you to
return `~Iteratorint`, once ~-objects work properly.
This is interesting. I assume we'd want these to be Iterator cast
