Inconsistency between operating on text object motions and standard motions

[Brennan Vincent]

If [count] is more than the number of objects available, operators with
motions operate on as many as possible.

For example: on a buffer with contents "x y z", "d5w" will delete from
the cursor to the end of the buffer.

Text object selection motions do not have this behavior. On a buffer
with contents "<<xyz>>", where the cursor is between the angles, "d5i<"
has no effect. Presumably it is being aborted because there are not
enough angle bracket pairs.

I'm not sure whether this is a bug or intended behavior, but I didn't
see it mentioned in the docs.