From caa564bea3d5f5a24d0797c4769184c1ea0abaff Mon Sep 17 00:00:00 2001 From: Patrick Walton Date: Mon, 21 Jul 2014 20:54:28 -0700 Subject: librustc: Stop desugaring `for` expressions and translate them directly. This makes edge cases in which the `Iterator` trait was not in scope and/or `Option` or its variants were not in scope work properly. This breaks code that looks like: struct MyStruct { ... } impl MyStruct { fn next(&mut self) -> Option { ... } } for x in MyStruct { ... } { ... } Change ad-hoc `next` methods like the above to implementations of the `Iterator` trait. For example: impl Iterator for MyStruct { fn next(&mut self) -> Option { ... } } Closes #15392. [breaking-change] --- src/test/debuginfo/lexical-scope-in-for-loop.rs | 1 + 1 file changed, 1 insertion(+) (limited to 'src/test/debuginfo') diff --git a/src/test/debuginfo/lexical-scope-in-for-loop.rs b/src/test/debuginfo/lexical-scope-in-for-loop.rs index 13cae3252d8..74d54624318 100644 --- a/src/test/debuginfo/lexical-scope-in-for-loop.rs +++ b/src/test/debuginfo/lexical-scope-in-for-loop.rs @@ -9,6 +9,7 @@ // except according to those terms. // ignore-android: FIXME(#10381) +// ignore-test: Not sure what is going on here --pcwalton // compile-flags:-g -- cgit 1.4.1-3-g733a5