rust/src/libstd/path, branch 0.10

Convert most code to new inner attribute syntax.

2014-03-29T00:12:21+00:00

Closes #2569

Changed `iter::Extendable` and `iter::FromIterator` to take a `Iterator` by value

2014-03-25T20:49:55+00:00

auto merge of #13090 : thestinger/rust/iter, r=Aatch

2014-03-23T09:41:53+00:00

This has been rendered obsolete by partial type hints. Since the `~[T]` type is in the process of being removed, it needs to go away.

iter: remove `to_owned_vec`

2014-03-23T09:41:23+00:00

This needs to be removed as part of removing `~[T]`. Partial type hints are now allowed, and will remove the need to add a version of this method for `Vec`. For now, this involves a few workarounds for partial type hints not completely working.

use TotalEq for HashMap

2014-03-23T05:59:11+00:00

Closes #5283

rename std::vec -> std::slice

2014-03-20T05:30:27+00:00

Closes #12702

std: allow io::File* structs to be hashable

2014-03-13T01:58:54+00:00

Use generic impls for `Hash`

2014-03-12T20:39:47+00:00

Removed DeepClone. Issue #12698.

2014-03-08T20:09:00+00:00

std: Change assert_eq!() to use {} instead of {:?}

2014-03-01T07:01:54+00:00

Formatting via reflection has been a little questionable for some time now, and it's a little unfortunate that one of the standard macros will silently use reflection when you weren't expecting it. This adds small bits of code bloat to libraries, as well as not always being necessary. In light of this information, this commit switches assert_eq!() to using {} in the error message instead of {:?}. In updating existing code, there were a few error cases that I encountered: * It's impossible to define Show for [T, ..N]. I think DST will alleviate this because we can define Show for [T]. * A few types here and there just needed a #[deriving(Show)] * Type parameters needed a Show bound, I often moved this to `assert!(a == b)` * `Path` doesn't implement `Show`, so assert_eq!() cannot be used on two paths. I don't think this is much of a regression though because {:?} on paths looks awful (it's a byte array). Concretely speaking, this shaved 10K off a 656K binary. Not a lot, but sometime significant for smaller binaries.