[
https://issues.apache.org/jira/browse/GROOVY-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450432#comment-15450432
]
John Wagenleitner commented on GROOVY-4018:
-------------------------------------------
Thanks for the feedback. I was trying to consolidate similar tickets around
this issue and I thought based on the title "comparisons with NaN should always
return false" that these were the same issue. I think this is slightly
different so am re-opening it.
> Make the Groovy truth value of NaN be false
> -------------------------------------------
>
> Key: GROOVY-4018
> URL: https://issues.apache.org/jira/browse/GROOVY-4018
> Project: Groovy
> Issue Type: Improvement
> Components: groovy-runtime
> Reporter: Steve Tekell
>
> Similar to null and empty-string, have Groovy evaluate NaN as false rather
> than true.
> def x = a?.b?.calcX(...)
> if (x) {
> // now I have a valid non-null number
> }
> This is how JavaScript treats NaN and like other Groovy design choices, it
> just makes sense.
> Discussed in this thread
> http://old.nabble.com/Shouldn't-the-Groovy-truth-value-of-NaN-be-false--tt27348256.html
> That is, if NaN was false the follow should work
> assert !(Double.NaN)
> assert !((Double.NaN as Boolean) == true)
> assert ((Double.NaN as Boolean) == false)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
