Hello,
coverage-data->lcov does not, and never has taken a 'modules'
argument, so I've removed it.
However, I would really like this, and might add it if it's not too hard.
From e0dbb70625d1dd850924122c64639994e2fed3b5 Mon Sep 17 00:00:00 2001
From: Peter Elliott <pelli...@ualberta.ca>
Date: Tue, 27 Aug 2019 20:19:15 -0700
Subject: [PATCH] Remove modules arg from coverage data->lcov doc
---
doc/ref/api-coverage.texi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/ref/api-coverage.texi b/doc/ref/api-coverage.texi
index 5081d343b..92ae606b6 100644
--- a/doc/ref/api-coverage.texi
+++ b/doc/ref/api-coverage.texi
@@ -25,12 +25,12 @@ Return @code{#t} if @var{obj} is a @dfn{coverage data} object as returned by
@code{with-code-coverage}.
@end deffn
-@deffn {Scheme Procedure} coverage-data->lcov data port #:key modules
+@deffn {Scheme Procedure} coverage-data->lcov data port
Traverse code coverage information @var{data}, as obtained with
@code{with-code-coverage}, and write coverage information to port in the
@code{.info} format used by @url{http://ltp.sourceforge.net/coverage/lcov.php,
-LCOV}. The report will include all of @var{modules} (or, by default, all the
-currently loaded modules) even if their code was not executed.
+LCOV}. The report will include all the modules loaded at the time coverage data was
+gathered, even if their code was not executed.
The generated data can be fed to LCOV's @command{genhtml} command to produce an
HTML report, which aids coverage data visualization.
--
2.22.1
