For that matter, why even have NaN to begin with?
-
@nikomatsakis non-stop execution of numerical code outside its domain of definition.
@graydon_moz thanks for the citation. It's unclear to me why an exception or Nan == nan wouldn't be better, will read (no doubt "tradeoffs")
-
-
@nikomatsakis@graydon_moz I am happy to take the time to help you understand the context and meaning from a numerical computing perspectiveThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@nikomatsakis apparently exceptions/traps imply prohibitively-expensive and hard-to-specify cross-language/cross-hardware control-flow model -
@graydon_moz@nikomatsakis It seems like implementing "NaN == NaN" shouldn't be any harder than "NaN != NaN"
End of conversation
New conversation -
-
-
@nikomatsakis I believe == vs. != has to do with "which set of violated algebraic identities is least bad?" numerical reasoning, don't know. -
@graydon_moz@nikomatsakis Sorry, missed this post. I also just found this: http://stackoverflow.com/questions/1565164/what-is-the-rationale-for-all-comparisons-returning-false-for-ieee754-nan-values …
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.