yeah, I can't think of any fix for this. Maybe a lint check could be written to warn you of "ambiguous statement resolution order" or something, but the code being compiled is still correct by all definitions of the word