Thank you, that was helpful!
--
You received this message because you are subscribed to the Google Groups
"Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-dev+unsubscr...@googlegroups.com.
To post to this group, send email to
Do you have any guess why the resulting numbers vary so much?
On Thursday, October 13, 2016 at 7:20:47 PM UTC+2, mflatt wrote:
>
> Thanks for the report!
>
> This is a bug in the optimizer's handling of `bitwise-and`, where I
> made it assume a fixnum result if either argument is a fixnum.
Hi all,
I get a weird behavior when using bitwise-ior and bitwise-and with large
numbers. Tested on 2 machines (racket 6.6, Ubuntu 16.04 and 14.04):
Here is the test example:
#lang racket
(define num #x) ;; remove one f, and the results are fine
in both cases
(for ([i 5])
