[NEW BUG]: Avoid allocations in String.replace(CharSequence, CharSequence) in case no replacement happened

Thu Mar 2 17:30:34 UTC 2017

Am 02.03.2017 um 18:16 schrieb Vitaly Davidovich:
> When the optimization applies, there shouldn't be *any* instructions for the null check on the 
> path - it's done via signal handling.
Thanks for clarification.

> This is Sufficiently Smart Compiler territory.  It's much better to hand-code this properly, 
> particularly since nothing is lost in readability or maintainability in this case.
Convinced!

-Ulf