Re: valid NaNs versus invalid NaNs?

Alternately Rhys, what Wes said. :) Donald E. Foss | @DonaldFoss Never Stop Learning! -- __o _`\<,_ ---(_)/ (_) > On Dec 10, 2018, at 11:23 AM, Donald Foss wrote: > > +1 on NaNs being an interop nightmare already, especially for those who work > with mu

Re: valid NaNs versus invalid NaNs?

+1 on NaNs being an interop nightmare already, especially for those who work with multiple coding languages at the same time. Issues regarding NaNs may be found at https://issues.apache.org/jira/browse/ARROW-2806?jql=text%20~%20%22NaN%22

RE: valid NaNs versus invalid NaNs?

>> Anyhow, it seems worth addressing this gap at the written specification >> level. > What would you suggest? We could add a statement to be explicit that no > special / sentinel values (which includes NaN) are recognized as null. I like your suggestion Wes. Please consider making that amendme

Re: valid NaNs versus invalid NaNs?

hi Rhys, On Mon, Dec 10, 2018 at 9:53 AM Rhys Ulerich wrote: > > 'Morning, > > > > Regarding https://arrow.apache.org/docs/memory_layout.html, how should > is_valid be interpreted for primitive types that have their own notions of > is_valid? > > > > Concretely, how should folks interpret a "va

valid NaNs versus invalid NaNs?

'Morning, Regarding https://arrow.apache.org/docs/memory_layout.html, how should is_valid be interpreted for primitive types that have their own notions of is_valid? Concretely, how should folks interpret a "valid NaN" (is_valid 1 with float NaN) versus an "invalid NaN" (is valid 0 with flo