Factor shared code out into default GenericPath methods.
Minor doc cleanup.
Replace os::glob with extra::glob, which is written in rust,
fixing issue #6100.
std::rt: Some I/O cleanup
std::rt: Add libuv bindings for getaddrinfo
std::rt: Add get_host_addresses function

This is a very simplistic method for host name resolution. It converts
a host name to a vector of IP addresses. Should be enough to get started.
std: Remove push_fast from OwnedVector. Closes #8769

This is an unsafe implementation detail of `push`.
Fix glitches with struct field aligned indents
Don't run lint over gyp files (they just fail anyway)
auto merge of #9011 : alexcrichton/rust/fix-lint, r=thestinger
auto merge of #8909 : lkuper/rust/default-methods-refactor, r=alexcrichton

 (cc: #3227)

Parts I'm unsure about and would like a reviewer to look at are:

  * `pub trait GenericPath : Clone + Eq + ToStr` -- is this the done thing?  I've never done trait inheritance before, let alone from multiple traits, but it seemed to be necessary to be able to call all the methods we have to be able to call on `self`.

  * changing the argument of `components` from `self` to `&self`, and having it return `self.components.clone()` instead of `self.components`; this was necessary to avoid move errors, but I'm not sure if it's the right thing.  (The default methods impls now all have to call `self.components()` instead of just referencing the field `self.components`.)
auto merge of #8914 : Dretch/rust/native-glob, r=alexcrichton

This is #8201 with a bunch of amendments to address the comments (and re-based).
Indent correctly after opening square bracket
Allow indenting to align struct fields after curly brace
Indent return type to align with arguments
Add custom group for rust-mode
Add paragraph fill and auto-fill for multi-line comments
Add ERT tests
std::rt: Fix addrinfo definition on BSD
Add fractional second support to str{p,f}time

The ISO 8601 standard does not mandate any specific precision for
fractional seconds, so this accepts input of any length, ignoring the
part after the nanoseconds place. It may be more correct to round with
the tenths of nanoseconds digit, but then we'd have to deal with
carrying the round through the entire Tm struct (e.g. for a time like
Dec 31 11:59.999999999999).

%f is the format specifier that Python's datetime library uses for
0-padded microseconds so it seemed appropriate here.

cc #2350