We're getting a little far from my real question, since caching the examples is
IMHO a hack to cache the most expensive part of the computation, while the whole
'doc ought to be cachable, but
I forgot what my own code was doing.
That's basically what I'm doing:
(define (make-cached-eval name
I'm not clear on what `with-cache` is doing in this setup, but it seems
like a potential source of errors. If the goal is to automatically use
`'replay` if the log file exists and `'record` otherwise, why not do the
following?
(make-log-based-eval the-log-file (if (file-exists? the-log-file)
On Wed, Mar 25, 2020 at 08:51:18PM +0100, Ryan Culpepper wrote:
> You can use `raco make` (or `raco setup` for docs of installed packages) to
> compile the Scribble files, but that won't compile the examples. Those are
> dynamically evaluated when the Scribble documents are run.
Yeah, I was
You can use `raco make` (or `raco setup` for docs of installed packages) to
compile the Scribble files, but that won't compile the examples. Those are
dynamically evaluated when the Scribble documents are run.
For `make-log-based-eval`, are you using a separate evaluator (and separate
log file)
Does Scribble support separate compilation or some kind of caching and I'm just
missing it?
I'm building a multi-page website using Scribble, with many @examples that take
a while to run.
If I touch *any page*, all the other pages have to rebuild, re-running the long
running examples.
I've
5 matches
Mail list logo
