groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Wagenleitner (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GROOVY-4018) Make the Groovy truth value of NaN be false
Date Sat, 01 Jul 2017 18:32:00 GMT

     [ https://issues.apache.org/jira/browse/GROOVY-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Wagenleitner updated GROOVY-4018:
--------------------------------------
    Labels: breaking  (was: )

> 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
>              Labels: breaking
>             Fix For: 3.x
>
>
> Similar to null and empty-string, have Groovy evaluate NaN as false rather than true.
> {noformat}
> def result = a?.b?.calcX(...)
> if (result) { 
>   // now I have a valid non-null number
> }
> {noformat}
> 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 following 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.4.14#64029)

Mime
View raw message