Automatic semicolon inference has a very big language footprint, similar to the range syntax that the author disliked.
Maybe not “very big”, but I agree with your point in principle.
The reason why I think it is worthwhile (compared to e. g. range syntax) is that we are paying for it anyway already:
Good error reporting hinges on parsing not strictly the language that’s defined, but understanding the language that people actually write – and people forget ; all the time.
So from my POV I’m turning an error reporting step (that I’d have to implement anyway) into something more useful.
For this feature to be useful, it has to be at least powerful enough to replace format!
To be honest, if all the fancy formatting stuff requires a macro, so be it.
I just don’t want to need macros for creating a list and so on.
Thank you for letting me know your thoughts!
Maybe not “very big”, but I agree with your point in principle.
The reason why I think it is worthwhile (compared to e. g. range syntax) is that we are paying for it anyway already:
Good error reporting hinges on parsing not strictly the language that’s defined, but understanding the language that people actually write – and people forget
;all the time.So from my POV I’m turning an error reporting step (that I’d have to implement anyway) into something more useful.
To be honest, if all the fancy formatting stuff requires a macro, so be it.
I just don’t want to need macros for creating a list and so on.