+1. As you correctly point out, this was caused by JDK-8043608. Strangely enough, I fixed the NaN case for strictEquals() with JDK-8044786, but I remember reasoning that it wasn’t an issue for equals(). Apparently, that was wrong…
Attila. > On Nov 23, 2015, at 3:35 PM, Hannes Wallnöfer <hann...@gmail.com> wrote: > > Please review JDK-8141407: Wrong evaluation of a != a when a = NaN: > > http://cr.openjdk.java.net/~hannesw/8141407/ > > Thanks, > Hannes
