Yes, this is clearly a bug.
At Fri, 29 Mar 2013 16:21:49 -0400, Vincent St-Amour wrote:
>
> I have found what I think may be a bug in Racket's constant propagation:
>
>(unsafe-fx* 0 (error 'foo))
>
> does not throw and error and evaluates to 0. If 0 is replaced with
> another value, or if i
I have found what I think may be a bug in Racket's constant propagation:
(unsafe-fx* 0 (error 'foo))
does not throw and error and evaluates to 0. If 0 is replaced with
another value, or if it's `read' in, the error is thrown.
`unsafe-fxquotient' has the same issue.
On the one hand, this is a
2 matches
Mail list logo
