fix the issue #103 by create two new FastCloners

[ZhenXiongQian]

To fix issue #103
In jdk 5, cloner.deepClone(Set.of(1)).size() will be 2 because EMPTY( it is null in jdk14 ) will be changed with clone. So it has to create new FastCloner.

[tweimer]

That is wrong, you must also clone the elements of the lists.

[ZhenXiongQian]

ok, I change the code to use cloner.deepClone

[ZhenXiongQian]

@tweimer is this pr ok now？

[tweimer]

See my comment in the review. A test for both cloners with two elements would be useful,for the sake of completeness.

[ZhenXiongQian]

the test cases are now complete

[tweimer]

Like good to me.

@kostaskougios has to merge it

[kostaskougios]

👍

[chadlwilson]

Assuming you feel this is stable at this stage, any chance of cutting another release @kostaskougios and @tweimer ?

[atribemc]

Any chance of 1.11.0 making it to maven central so i can get this fix?

[chadlwilson]

@atribemc Seems unlikely based on #105 (comment)

I did start to consider maintaining/releasing a fork at https://github.com/chadlwilson/cloning but haven't pushed it anywhere yet/set up automation, as for my use case we had our own fast cloners for the issue in this PR and we needed --add-opens anyway making the other unreleased Java 16 fixes not so relevant.

I'm not sure if any other possible fork candidates have emerged...