typo & multi-precision Jim Rees (29 Aug 2020 18:06 UTC)
Re: typo & multi-precision John Cowan (30 Aug 2020 00:32 UTC)
Re: typo & multi-precision Jim Rees (30 Aug 2020 23:22 UTC)
Re: typo & multi-precision Wolfgang Corcoran-Mathe (31 Aug 2020 15:58 UTC)
Re: typo & multi-precision Wolfgang Corcoran-Mathe (01 Sep 2020 01:27 UTC)
Re: typo & multi-precision Shiro Kawai (30 Aug 2020 22:42 UTC)
Re: typo & multi-precision Lucier, Bradley J (31 Aug 2020 00:44 UTC)

Re: typo & multi-precision Wolfgang Corcoran-Mathe 31 Aug 2020 15:58 UTC

On 2020-08-29 20:32 -0400, John Cowan wrote:
> > 3) make do the comparison only after converting the lower precision nan to
> > the higher precision nan first.
> >
> > #3 makes the most sense to me
> >
>
> I agree.  Added text:
>
> If <em>nan1</em> and <em>nan2</em> are of different precisions,
> the lower-precision value is converted to at least the precision
> of the other value.

Is there anything a portable implementation can do to cover this?
Since we lack (I believe) procedures to inspect precision, would some
sort of ad-hoc test comparing the results of both
bytevector-ieee-single-set! and bytevector-ieee-double-set! be
necessary?

--
Wolfgang Corcoran-Mathe  <xxxxxx@sigwinch.xyz>

"If one is searching for a needle in a haystack, look in the part
of the haystack that contains more needles." --Bird & Wadler