> For example, it could use semicolons if some proc declaration in the source > code file already uses semicolons.
The semantic difference between using them and not using them makes this kind of detection fickle at best - there are many edge cases and irregularities in the parser - ditto can be said of most "controversial" cases, ie making something that works (ie doesn't break on unusual cases) and guesses the intentions right makes for complex code. It's sort of possible to reverse engineer the parser and the strange quirks that have been added over time and create a use-commas-where-possible rule but that adds quite a bit of complexity and results in code that sometimes for (to mere mortals) inexplicable reasons inserts `;` \- I'm somewhat hesitant for this reason. More broadly, it defeats the purpose of the tool (which is to focus on efficient collaboration across the ecosystem for participating projects).
