Tracking issue for iter::range_inclusive

[alexcrichton]

This is a tracking issue for the unstable range_inclusive feature in the standard library. This will likely be deprecated and removed if rust-lang/rfcs#1192 is accepted. Otherwise this will likely be deprecated and removed in favor of a builder-style interface on Range

[BurntSushi]

Now that rust-lang/rfcs#1192 has been accepted, can we deprecate this?

[alexcrichton]

This issue is now entering its cycle-long FCP for deprecation in 1.5

[alexcrichton]

The libs team discussed this during triage today and the decision was to deprecated.