It's subtle, but I think the difference is that in ruby when potentially_falsy_v... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

nimblegorilla on Jan 20, 2015 | parent | context | favorite | on: The Groovy project is looking for a new home

It's subtle, but I think the difference is that in ruby when potentially_falsy_value is false you will get the safeDefault. But with ?: you would get the potentiallyFalsyValue as false. The only time you get safeDefault is when potentiallyFalsyValue is nil/null

prophetjohn on Jan 22, 2015 [–]

The docs seem to state otherwise

   One instance of where this is handy is for 
   returning a 'sensible default' value if an 
   expression resolves to false or null

http://groovy.codehaus.org/Operators#Operators-ElvisOperator(?:)

Consider applying for YC's Spring batch! Applications are open till Feb 11.
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact