Consider the Lua programming language, which has the following constructs involving the keywords do and end:
do-endwhile <cond> do-endfor <...> do-end
If I were to add do-while <cond>; statements (the semicolon would be optional, but for the sake of simplicity we can assume that it's mandatory to exclude possibly of the part of <cond> being considered a <prefixexp> of the following statement).
I seemingly can't construe any ambiguity, but it looks like this might significantly complicate the parsing: When a do is encountered, it may end with either an end or a while; however a while may also be a nested while-do-end inside the do block.
Which issues would you see with adding do-while given Lua's current use of the while, do and end keywords?
(I'm aware that do-while would be largely redundant with repeat-until; I'm also wondering why the Lua authors preferred repeat-until, and I feel that parsing considerations may have been a factor)