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

Should TR optimizer docs recommend real->double-flonum (#498)

Browse Source 
instead of exact->inexact?

Since its usage in the guide is to create a value of type Float on which TR can apply optimizations, real->double-flonum seems like the the better choice. The type of exact->inexact can sometimes produce single flonums or complex numbers, but real->double-flonum always returns a Float.

For converting exact complex numbers into inexact complex numbers I don't see another option; I'm not sure what to do there.
This commit is contained in:
Alex Knauth 2017-10-01 17:36:23 -04:00 committed by Andrew Kent
parent d106797238
commit 4465273da2
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
typed-racket-doc/typed-racket/scribblings/guide/optimization.scrbl
View File

@ -73,8 +73,8 @@ 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[-]. When mixing
reals to floating-point numbers using @racket[real->double-flonum].
This is not necessary when using @racket[+] or @racket[-]. When mixing
floating-point numbers of different precisions, results use the
highest precision possible.