about summary refs log tree commit diff
path: root/src
diff options
context:
space:
mode:
authorAlex Crichton <alex@alexcrichton.com>2015-02-09 16:24:29 -0800
committerAlex Crichton <alex@alexcrichton.com>2015-02-09 16:26:52 -0800
commit0ee95b917b30d7a48bcafa8b4642f3bcec4d50ff (patch)
treefd77a8653e2d77e28f23344c1d281751475548f6 /src
parent605225a366b62f29f5fd4b03cc298fff03bc3bdf (diff)
downloadrust-0ee95b917b30d7a48bcafa8b4642f3bcec4d50ff.tar.gz
rust-0ee95b917b30d7a48bcafa8b4642f3bcec4d50ff.zip
std: Mark IntoIterator::into_iter as #[stable
Right now it is not possible to write a `for` loop without opting-in to the
`core` feature due to the way they're expanding (calling
`::std::iter::IntoIterator::into_iter`). There are some planned tweaks to the
`IntoIterator` trait (adding an `Item` associated type) which will cause
implementations of `IntoIterator` to break, but the *usage* of the trait is
currently stable.

This commit marks the method `into_iter` as stable as the name will not be
changing, nor the fact that it takes no arguments and returns one type (which is
determiend by the `Self` type). This means that usage of `for` loops is now
stable but manual implementations of the `IntoIterator` trait will continue to
be unstable.
Diffstat (limited to 'src')
-rw-r--r--src/libcore/iter.rs1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/libcore/iter.rs b/src/libcore/iter.rs
index 2d240a53c4f..20cd1c30839 100644
--- a/src/libcore/iter.rs
+++ b/src/libcore/iter.rs
@@ -123,6 +123,7 @@ pub trait IntoIterator {
     type IntoIter: Iterator;
 
     /// Consumes `Self` and returns an iterator over it
+    #[stable(feature = "rust1", since = "1.0.0")]
     fn into_iter(self) -> Self::IntoIter;
 }