Q: ANTLR: bug in setUnknownTokenBoundaries()? CommonTree#setUnknownTokenBoundaries()  updates token boundaries of an AST node by using the boundaries of the node's first and last child.  This seems to assume that the children of the AST are ordered by the token order.  However, such an ordering is not enforced when constructing ASTs.
Is this a bug?  Should setUnknownTokenBoundaries() be updated to pick the min/max among all of the children instead of just using the first and last child?  Or am I missing something...
Thanks in advance.
