Hi Alex, Matt, and Gilles,
As discussed on the other thread, I have made NUMBERS-186 (for complex
lists work) the child of a parent ticket (NUMBERS-187)
I have created NUMBERS-188 for the functional interfaces and static method
refactoring of the existing instance methods of Complex class.
I
Is someone able to confirm that the
METHOD_NO_LONGER_THROWS_CHECKED_EXCEPTION japicmp compatibility change
is something we're ok with between releases? Note that this is a
binary compatible change but not a source compatible one.
Regards,
Matt J
On Sun, Jun 19, 2022 at 10:50 AM Matt Juntunen
Hello,
The throw clauses in question are on protected methods. If a user had
overridden these and then thrown an exception, they may have to modify
their source in order to compile against 2.8. Is this ok from the
point of view of our backwards compatibility guarantees?
Regards,
Matt J
On Sun,
This change is incorrect, binary compatibility was NOT broken as the JLS
specifies that:
"Changes to the throws clause of methods or constructors do not break
compatibility with pre-existing binaries; these clauses are checked only at
compile time."
See
