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

Documented TR's behavior when mixing exactness.

Browse Source
This commit is contained in:
Vincent St-Amour 2010-08-11 20:00:01 -04:00
parent 3d071b479e
commit cf692e986d
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
collects/typed-scheme/scribblings/optimization.scrbl
View File

@ -58,6 +58,14 @@ Thus, to get the most of Typed Racket's optimizer, you should use the
floating-point literals instead of exact literals when doing floating-point literals instead of exact literals when doing
floating-point computations. floating-point computations.
When mixing floating-point numbers and exact reals in arithmetic
operations, the result is not necessarily a @racket[Float]. For
instance, the result of @racket[(* 2.0 0)] is @racket[0] which is not
a @racket[Float]. This can result in missed optimizations. To prevent
this, when mixing floating-point numbers and exact reals, coerce exact
reals to floating-point numbers using @racket[exact->inexact]. This is
not necessary when using @racket[+] or @racket[-].
On a similar note, the @racket[Inexact-Complex] type is preferable to On a similar note, the @racket[Inexact-Complex] type is preferable to
the @racket[Complex] type for the same reason. Typed Racket can keep the @racket[Complex] type for the same reason. Typed Racket can keep
@tech[#:doc '(lib "scribblings/reference/reference.scrbl") #:key @tech[#:doc '(lib "scribblings/reference/reference.scrbl") #:key