Add getChars to CharSequence

Martin Buchholz martinrb at
Tue Apr 23 19:55:49 UTC 2013

Yes, all-or-nothing behavior on errors is worth something, and we should
get it right, especially when it's cheap.

On Tue, Apr 23, 2013 at 4:52 AM, Alan Bateman <Alan.Bateman at>wrote:

> One other observation, but as the 2-arg getChars doesn't have explicit
> bounds checking then it may have have copied some chars into the
> destination array before it throws the AIOOBE. Not too interesting of
> course but it may be worth considering a check before copying.
> -Alan.

More information about the core-libs-dev mailing list