RFR: 8026369: javac potentially ambiguous overload warning needs an improved scheme [v3]

Fri Feb 24 20:24:05 UTC 2023

On Fri, 24 Feb 2023 20:05:52 GMT, Archie L. Cobbs <duke at openjdk.org> wrote:

>> I'm not saying that we should de-stream the code, actually we can do that later on, in a separate issue, iff there is a performance related complain, but it is true that in the past, I have seen some performance issues and the final culprit have been streams. But you are right it could be that it is not worthy to affect the readability of the code.
>
> OK thanks, I'll leave it for now - but it would be nice to (someday) do some comprehensive testing so we have a better intuitive understanding of the performance impact of using a `Stream` in any particular situation.
> 
> I wonder if there is some IDE tool that could automatically `Stream`ify and/or de-`Stream`ify loops. If so, we could apply it to the entire compiler and compare...

yes that would be nice to have, although streams have different effects depending on how hot the code path is, so in general they are OK. Inference code is one of the places where I have seen that using streams is not a good idea for example

-------------

PR: https://git.openjdk.org/jdk/pull/12645