Future.resultNow()

[Pedro Lamarão]

Em dom., 21 de nov. de 2021 às 08:30, Ron Pressler <ron.pressler at oracle.com>
escreveu:


> I don’t think that wrapping the underlying exception, if there is one,
> would be helpful in pinpointing the bug. If the ISE tells you it’s caused
> by an exception, you know you need to correct the program by adding code to
> handle exceptions or filter them. What the original exception was is
> irrelevant.
>


I agree with this point and I think that there is a misguided notion of
"usability" being defended.
If there is a bug that when activated triggers executing invalid code,
which is another bug,
it may appear that it will be economical to log these two bugs at once, but
I think this is a mistake.
Whenever one reads a stack trace with inner exceptions,
there is a strong force towards considering the inner exception as being
somehow the "true bug"
and the outer exception as being merely an unfortunate accident.
It is counter intuitive that the "inner exception" is a completely
different bug than the "outer exception".

-- 
Pedro Lamarão
https://www.prodist.com.br
Securing Critical Systems
Tel: +55 11 4380-6585

Antes de imprimir esta mensagem e seus anexos, certifique-se que seja
realmente necessário.
Proteger o meio ambiente é nosso dever.
Before printing this e-mail or attachments, be sure it is necessary.
It is in our hands to protect the environment.