Re: feature/native-comp 5bc0855 2/2: Don't treat '=' as simple equality emitting constraints (bug#46812)

[Andrea Corallo]

Pip Cet <pipcet@gmail.com> writes:

> On Tue, Mar 2, 2021 at 1:47 PM Andrea Corallo <akrl@sdf.org> wrote:
>> > It's not working either, as far as I can tell: (lambda (x) (and
>> > (floatp x) (= x 0) x)) always returns nil when compiled.
>>
>> Right, I think a better approach is to relax the inputs before
>> intersecting them so intersection is not cutting off already constrained
>> inputs.
>
> That should work.
>
>> 8c7228e8cd for now follows this conservative approach and adds
>> some testing for the case.
>
> Indeed, and it breaks trying to compile (lambda (x) (unless (= x
> 1.0e+INF) (error "")) x). (And please don't forget NaNs, they're
> numbers too! Except they're not.)

Is there a better way to guard against these cases than catching the
error around truncate?

  Andrea