>But my point is that with the introduction of Iterable into the java >libraries, programmer __expect__ to be able to iterate over list-like >things.
Understood. However, we view iteration as a convenience more than a requirement. Sequence is meant to be more of a workhorse, providing functionality along the lines of what you might expect from an array. Classes that implement Sequence can provide higher-level functionality like iteration. >I don't see that adding a new type IterableSequence and making it the >default in the wtk API would add any extra overhead - you could keep >doing your style for-loops, and I could have mine :-) It doesn't add much overhead, but it does feel a bit ugly. Were there specific instances where you expected to find an iterable sequence but didn't? Maybe we can address them individually, rather than making a sweeping change across the entire API.
