Document that concurrent modification is bad, m'kay.

sdk/lib/core/iterable.dart

Index: sdk/lib/core/iterable.dart
diff --git a/sdk/lib/core/iterable.dart b/sdk/lib/core/iterable.dart
index 42ecd46652decb7d73fd399d9ac41332770d25e3..ed4ebcc8f10c2fdfd5513c64d5f2dbdc01aee6de 100644
--- a/sdk/lib/core/iterable.dart
+++ b/sdk/lib/core/iterable.dart
@@ -25,6 +25,11 @@ part of dart.core;
  * You can implement Iterable in your own class.
  * If you do, then an instance of your Iterable class
  * can be the right-hand side of a for-in construct.
+ *
+ * Some subclasss of `Iterable` can be modified. It is generally not allowed
+ * to modify such collections while they are being iterated. Doing so will break
+ * the iteration, which is typically signalled by throwing a
+ * [CuncurrentModificationError] when it is detected.

[karlklose, 2013/10/15 14:15:14]

CuncurrentModificationError -> C*o*ncurrentModificationError.

[Lasse Reichstein Nielsen, 2013/10/16 05:41:24]

Ack, thanks.

  */
 abstract class Iterable<E> {
   const Iterable();