Thanks for the info!
For the use case I found, the override does not make any sense and a final
method would have allowed for an easy fix if that would have been the way
this was discovered.
I think the method would make sense even before Loom. The overridable
getter is also used in some MX beans
On 25/03/2022 08:18, Rafael Winterhalter wrote:
Hello,
I was recently debugging an issue where threads' ids were used to identify
an origin thread. The issue turned out to be that the getId method was
overridden to return 0 for a row of threads in unrelated code, what broke
that processing.
I d
Hello,
I was recently debugging an issue where threads' ids were used to identify
an origin thread. The issue turned out to be that the getId method was
overridden to return 0 for a row of threads in unrelated code, what broke
that processing.
I do now wonder if it would be a good idea to offer a
