Confusing error when using do instead of for

[brson]

Range should have been called with for

./uuid.rs:90:41: 99:9 error: mismatched types: expected `bool` but found `()` (bool vs ())
./uuid.rs:90         do uint::range(0u, 100000u) |_i| {
./uuid.rs:91             let uuid = uuid();
./uuid.rs:92             assert uuid == from_str(to_str(uuid));
./uuid.rs:93
./uuid.rs:94             let uuid = uuid_random();
./uuid.rs:95             assert uuid == from_str(to_str(uuid));

[kud1ing]

If we'd remove the do-expression and rename for to do, what would we lose?

[brson]

@Lenny222 for only handles functions where the operator is a stack closure returning bool. Things like map and spawn won't work with it.

We could possibly have one keyword that just does the right thing based on the closure type. do x.each { doesn't sound so bad. for spawn { isn't great.

[kud1ing]

Having only a do "do"-ing the right thing sounds like a win.

[bblum]

Seems like the typechecker should attempt to see if "for" would have been the right thing, and said "Did you mean 'for'?". (Same for the other way around.)

[pcwalton]

@Lenny222 I feel like that would be too magical. Silently inserting the equivalent of return true at the end of a lambda, without a special form to indicate this is happening, doesn't sit right with me.