Yes yes, technically this is also a parser ambiguity issue; you can stop it either way and should fix both.