End positions are only stored for some tree kinds. There is logic in TreeInfo.getEndPos that looks for an end position on an enclosing node, for trees that don't have their own end position.

After the changes in JDK-8372948 end positions are stored directly in a field that is present in all tree kinds, instead of in a separate map, so it would be possible to store end positions directly on more or all trees, and avoid the logic in TreeInfo.getEndPos.

This bug tracks investigating that cleanup, and removing the switch from TreeInfo.getEndPos. This idea was proposed in the review thread for JDK-8372948.