non-non-non-optional semicolons give horrible error messages - LOW SEVERITY about dafny HOT 3 OPEN

I think the pattern is that statements ending in }, such as loops and conditionals, and statements with a by clause, do not need an ; after the }.

What change are you suggesting?

I trust you when you say the current behavior is confusing, but it would help to have an idea of how to improve it.

from dafny.

Marking as enhancement not bug, since this is documented behavior.

from dafny.

• what to change - permitting "empty" statements - sequences of semicolons - may be the easiest fix. makes this less sensitive

• I'm not that bothered by Python-style omitted semicolons, so I'm not the best person to ask.

• I think we did a good job in Grace, or at least one I personally liked (semicolons are optional, layout is used to do secondary grouping. I thought it was philosophically the worst of both worlds, but it seemed to work quite nicely!

• but with Dafny now sometimes looking at layout to give hints, etc, and general inconsistency, perhaps we've been piped at the post?

• OK, I can list such things as enhanements in future

from dafny.