we also correctly take advantage of the starting byte offset of the
parent decl when calling `tree.tokenLocation()`!