suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixed a bug in typed Scheme's optimizer when using binary arithmetic

Browse Source 
operators in a unary fashion with floats.
This commit is contained in:
Vincent St-Amour 2010-05-21 10:59:50 -04:00
parent 664ef2c0a3
commit 762f108c04
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
collects/typed-scheme/private/optimize.rkt
View File

@ -60,11 +60,11 @@
(begin (log-optimization "unary float" #'op) (begin (log-optimization "unary float" #'op)
#'(op.unsafe f.opt))) #'(op.unsafe f.opt)))
;; unlike their safe counterparts, unsafe binary operators can only take 2 arguments ;; unlike their safe counterparts, unsafe binary operators can only take 2 arguments
(pattern (#%plain-app op:float-binary-op f fs ...) (pattern (#%plain-app op:float-binary-op f1 f2 fs ...)
#:with opt #:with opt
(begin (log-optimization "binary float" #'op) (begin (log-optimization "binary float" #'op)
(for/fold ([o #'f.opt]) (for/fold ([o #'f1.opt])
([e (syntax->list #'(fs.opt ...))]) ([e (syntax->list #'(f2.opt fs.opt ...))])
#`(op.unsafe #,o #,e)))) #`(op.unsafe #,o #,e))))
(pattern (#%plain-app op:pair-unary-op p) (pattern (#%plain-app op:pair-unary-op p)
#:with opt #:with opt