On Thu, 31 Oct 2024 13:29:35 GMT, Claes Redestad wrote:
> Benchmarks using Indify was added to the JMH microbenchmarks corpus in the
> JDK 8 timeframe. This adds overhead to the microbenchmarks build and has been
> blocking/slowing progress on some indy-based prototyping as the indify tool
> i
On Thu, 31 Oct 2024 13:29:35 GMT, Claes Redestad wrote:
> Benchmarks using Indify was added to the JMH microbenchmarks corpus in the
> JDK 8 timeframe. This adds overhead to the microbenchmarks build and has been
> blocking/slowing progress on some indy-based prototyping as the indify tool
> i
On Thu, 31 Oct 2024 13:29:35 GMT, Claes Redestad wrote:
> Benchmarks using Indify was added to the JMH microbenchmarks corpus in the
> JDK 8 timeframe. This adds overhead to the microbenchmarks build and has been
> blocking/slowing progress on some indy-based prototyping as the indify tool
> i
On Thu, 31 Oct 2024 13:56:42 GMT, Chen Liang wrote:
>> Benchmarks using Indify was added to the JMH microbenchmarks corpus in the
>> JDK 8 timeframe. This adds overhead to the microbenchmarks build and has
>> been blocking/slowing progress on some indy-based prototyping as the indify
>> tool i
On Thu, 31 Oct 2024 13:29:35 GMT, Claes Redestad wrote:
> Benchmarks using Indify was added to the JMH microbenchmarks corpus in the
> JDK 8 timeframe. This adds overhead to the microbenchmarks build and has been
> blocking/slowing progress on some indy-based prototyping as the indify tool
> i
Benchmarks using Indify was added to the JMH microbenchmarks corpus in the JDK
8 timeframe. This adds overhead to the microbenchmarks build and has been
blocking/slowing progress on some indy-based prototyping as the indify tool
itself may not be 100% forward compatible.
I suggest we remove the
