From 02a267fdb290f8729be96b9c7cb04ac18363441a Mon Sep 17 00:00:00 2001 From: Robby Findler Date: Wed, 21 Dec 2016 12:34:59 -0600 Subject: [PATCH] clarify that futures don't run in parallel with errortrace --- pkgs/racket-doc/scribblings/guide/futures.scrbl | 4 +++- pkgs/racket-doc/scribblings/guide/performance.scrbl | 4 +++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/pkgs/racket-doc/scribblings/guide/futures.scrbl b/pkgs/racket-doc/scribblings/guide/futures.scrbl index 63c8c867dc..3adcfdaa52 100644 --- a/pkgs/racket-doc/scribblings/guide/futures.scrbl +++ b/pkgs/racket-doc/scribblings/guide/futures.scrbl @@ -13,7 +13,9 @@ The @racketmodname[racket/future] library provides support for performance improvement through parallelism with @deftech{futures} and the @racket[future] and @racket[touch] functions. The level of parallelism available from those constructs, however, is limited by several factors, and the -current implementation is best suited to numerical tasks. +current implementation is best suited to numerical tasks. The caveats +in @secref["DrRacket-perf"] also apply to futures; notably, +the debugging instrumentation currently defeats futures. @margin-note{Other functions, such as @racket[thread], support the creation of reliably concurrent tasks. However, threads never run truly diff --git a/pkgs/racket-doc/scribblings/guide/performance.scrbl b/pkgs/racket-doc/scribblings/guide/performance.scrbl index e647146b2c..eed8ca7e13 100644 --- a/pkgs/racket-doc/scribblings/guide/performance.scrbl +++ b/pkgs/racket-doc/scribblings/guide/performance.scrbl @@ -28,7 +28,9 @@ and memory performance of Racket code. @section[#:tag "DrRacket-perf"]{Performance in DrRacket} By default, DrRacket instruments programs for debugging, and -debugging instrumentation can significantly degrade performance for +debugging instrumentation (provided by the +@other-doc['(lib "errortrace/scribblings/errortrace.scrbl")] +library) can significantly degrade performance for some programs. Even when debugging is disabled through the @onscreen{Choose Language...} dialog's @onscreen{Show Details} panel, the @onscreen{Preserve stacktrace} checkbox is clicked by default,