FYI
Forwarded Message
Subject:Project Wakefield announcement and welcome
Date: Wed, 1 Sep 2021 14:59:30 -0700
From: Philip Race
To: wakefield-...@openjdk.java.net
Hi all,
The project has been recorded in the OpenJDK census :
> Usage of thread-safe collection `Vector` is unnecessary. It's recommended to
> use `ArrayList` if a thread-safe implementation is not needed. In
> post-BiasedLocking times, this is gets worse, as every access is synchronized.
> I checked only places where `Vector` was used as local variable.
> Usage of thread-safe collection `Vector` is unnecessary. It's recommended to
> use `ArrayList` if a thread-safe implementation is not needed. In
> post-BiasedLocking times, this is gets worse, as every access is synchronized.
> I checked only places where `Vector` was used as local variable.
On Fri, 27 Aug 2021 18:28:58 GMT, Sergey Bylokhov wrote:
>> Can you please elaborate?
>> As I can see if size of array is exactly the same as size of
>> vector/arraylist, implementations are similar - they just call
>> System.arraycopy
>>
> parseInt/parseLong/parseShort/parseByte/parseFloat should be preferred, as
> they return primitives. While valueOf returns boxed object.
Andrey Turbanov has updated the pull request with a new target base due to a
merge or a rebase. The incremental webrev excludes the unrelated changes
On Tue, 31 Aug 2021 20:04:23 GMT, Сергей Цыпанов
wrote:
>> Just a very tiny clean-up.
>>
>> There are some places in JDK code base where we call
>> `Enum.class.getEnumConstants()` to get all the values of the referenced
>> `enum`. This is excessive, less-readable and slower than just calling
