On Thu, 1 Dec 2022 08:14:07 GMT, Sergey Tsypanov wrote:
>> `String.offsetByCodePoints()` delegates to `Character.offsetByCodePoints()`
>> which in turn specifies the same exception thrown under the same conditions
>> and the implementation does exactly the same checks. This means we can
>>
On Thu, 1 Dec 2022 08:14:07 GMT, Sergey Tsypanov wrote:
>> `String.offsetByCodePoints()` delegates to `Character.offsetByCodePoints()`
>> which in turn specifies the same exception thrown under the same conditions
>> and the implementation does exactly the same checks. This means we can
>>
> `String.offsetByCodePoints()` delegates to `Character.offsetByCodePoints()`
> which in turn specifies the same exception thrown under the same conditions
> and the implementation does exactly the same checks. This means we can remove
> the check from `String.offsetByCodePoints()` and rely on
> `String.offsetByCodePoints()` delegates to `Character.offsetByCodePoints()`
> which in turn specifies the same exception thrown under the same conditions
> and the implementation does exactly the same checks. This means we can remove
> the check from `String.offsetByCodePoints()` and rely on
On Wed, 30 Nov 2022 20:41:47 GMT, Claes Redestad wrote:
>> Sergey Tsypanov has updated the pull request with a new target base due to a
>> merge or a rebase. The incremental webrev excludes the unrelated changes
>> brought in by the merge/rebase. The pull request contains three additional
>>
On Wed, 30 Nov 2022 18:17:47 GMT, Sergey Tsypanov wrote:
>> `String.offsetByCodePoints()` delegates to `Character.offsetByCodePoints()`
>> which in turn specifies the same exception thrown under the same conditions
>> and the implementation does exactly the same checks. This means we can
>>
On Wed, 30 Nov 2022 18:17:47 GMT, Sergey Tsypanov wrote:
>> `String.offsetByCodePoints()` delegates to `Character.offsetByCodePoints()`
>> which in turn specifies the same exception thrown under the same conditions
>> and the implementation does exactly the same checks. This means we can
>>
On Thu, 24 Nov 2022 10:08:31 GMT, Sergey Tsypanov wrote:
> `String.offsetByCodePoints()` delegates to `Character.offsetByCodePoints()`
> which in turn specifies the same exception thrown under the same conditions
> and the implementation does exactly the same checks. This means we can remove
> `String.offsetByCodePoints()` delegates to `Character.offsetByCodePoints()`
> which in turn specifies the same exception thrown under the same conditions
> and the implementation does exactly the same checks. This means we can remove
> the check from `String.offsetByCodePoints()` and rely on
On Thu, 24 Nov 2022 10:08:31 GMT, Sergey Tsypanov wrote:
> `String.offsetByCodePoints()` delegates to `Character.offsetByCodePoints()`
> which in turn specifies the same exception thrown under the same conditions
> and the implementation does exactly the same checks. This means we can remove
`String.offsetByCodePoints()` delegates to `Character.offsetByCodePoints()`
which in turn specifies the same exception thrown under the same conditions and
the implementation does exactly the same checks. This means we can remove the
check from `String.offsetByCodePoints()` and rely on the one
11 matches
Mail list logo