It was done less so for execution and showing non-errors and more so for other features like Code Insight and Explain Plan. A lot of folks still cling to Ctrl+Enter to execute code. That logic uses blank lines as statement terminators. However, most every other feature in Editor relies heavily on the parser. Code Insight, Explain Plan, etc. would not function unless the entire editor text was valid code including proper statement termination. So, we provide a new option that forces the parser to abide by legacy rules where blank line is terminator.
A common use case for blank line termination would be a select with union or subqueries. If you want to test an individual piece of a larger statement you can select the text you want to test and execute. With this option you can just place a blank line to isolate the piece. Blank line is an easier option in some cases. There have been countless examples over the years demonstrating its usefulness both here and through official support channels.
You’re asking the wrong question. Ask instead who wants to be required to use proper syntax throughout their entire editor text to ensure Code Insight, Explain Plan, and other features function? I think you’ll get a different set of responses.
You at least have a workaround, turn off the option. Prior to the option the other users who have used Toad for 10+ years and were used to old way of doing things have been left out in the cold. For the record, I’m in your camp.