Add test program to verify compile-time error if no type in for-in loop

[jafingerhut]

No description provided.

[kfcripps]

I think it would make sense to improve the parser errors in general. This is not just a matter of missing type if loops, the parser errors are quite confusing and hard to read in general. I'm not sure how much does the parser generator allow for customization of them though...

We also have #2478 that is related to this :)

[ChrisDodd]

I think it would make sense to improve the parser errors in general. This is not just a matter of missing type if loops, the parser errors are quite confusing and hard to read in general. I'm not sure how much does the parser generator allow for customization of them though...

We also have #2478 that is related to this :)

In general, to improve these parse errors, you need to add code (rules) to the bison parser that matches in the problematic cases and then emits a more specific/better error. Doing this without introducing conflicts and breaking things that should work is sometimes tricky.