I would try to solve the ambiguity by doc-patching anyway, although
defining the execution line is complex ( in things like loops when
looping etc.. ). I am used to that and do not thing the extra
bug-surface introduced by the detailed accounting is worthwile.
Perhaps the best docs patch is to simply state the nature of the ambiguity. Something like, "For a statement spanning more than one line, the precise line reported could be the line on which the statement begins, the line on which it ends, or any line in between, regardless of which specific part of the statement is actually executing."
That would prevent the confusion raised here without increasing the bug surface or constraining future changes to the language, including in bugfix releases.
