This gives a better diagnostic in general, because it indicates that the user didn't
close out the last open puncutation range. For example:
foo.op { some.op -> !blah.pointer< }
We want the error to hint about the unclosed <, not the } (which isn't really in the context of the type).
Depends on D140199