Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upTracking issue for iter::range_inclusive #27777
Comments
alexcrichton
added
T-libs
B-unstable
labels
Aug 13, 2015
This comment has been minimized.
This comment has been minimized.
|
Now that rust-lang/rfcs#1192 has been accepted, can we deprecate this? |
alexcrichton
added
E-easy
I-nominated
labels
Sep 17, 2015
This comment has been minimized.
This comment has been minimized.
|
This issue is now entering its cycle-long FCP for deprecation in 1.5 |
alexcrichton
added
final-comment-period
and removed
I-nominated
labels
Sep 24, 2015
steveklabnik
added this to the 1.5 milestone
Oct 1, 2015
Manishearth
removed
the
E-easy
label
Oct 2, 2015
This comment has been minimized.
This comment has been minimized.
|
The libs team discussed this during triage today and the decision was to deprecated. |
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Oct 23, 2015
bors
added a commit
that referenced
this issue
Oct 24, 2015
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Oct 24, 2015
bors
added a commit
that referenced
this issue
Oct 25, 2015
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Oct 25, 2015
bors
added a commit
that referenced
this issue
Oct 25, 2015
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Oct 25, 2015
bors
added a commit
that referenced
this issue
Oct 25, 2015
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Oct 25, 2015
bors
added a commit
that referenced
this issue
Oct 25, 2015
bors
closed this
in
#29254
Oct 25, 2015
arcnmx
added a commit
to arcnmx/rust
that referenced
this issue
Nov 2, 2015
bors
added a commit
that referenced
this issue
Mar 5, 2016
bors
added a commit
that referenced
this issue
Mar 6, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
alexcrichton commentedAug 13, 2015
This is a tracking issue for the unstable
range_inclusivefeature 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 onRange