branch: externals/compat
commit f0362f354c03beeb677660ce1441c53e25a29191
Author: Daniel Mendler <[email protected]>
Commit: Daniel Mendler <[email protected]>

    Warn about untested functions
---
 compat-tests.el |  4 ++--
 compat.texi     | 10 +++++-----
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/compat-tests.el b/compat-tests.el
index 5334e3de62..63d81971ce 100644
--- a/compat-tests.el
+++ b/compat-tests.el
@@ -21,8 +21,8 @@
 ;;
 ;; Note that not all functions have tests yet.  Grep the Compat code for
 ;; <UNTESTED> labels.  If you intend to use a function, which doesn't have
-;; tests yet, please contribute tests here.  NO GUARANTEES ARE MADE FOR
-;; FUNCTIONS WITHOUT TESTS.
+;; tests yet, please contribute tests here.  FUNCTIONS WITHOUT TESTS SHOULD
+;; BE CONSIDERED BROKEN.
 
 ;; The tests are written in a simple, explicit style.  Please inspect the
 ;; tests in order to find out the supported calling conventions.  In
diff --git a/compat.texi b/compat.texi
index baa38af716..1527a2e947 100644
--- a/compat.texi
+++ b/compat.texi
@@ -146,11 +146,11 @@ call these definitions ``Explicit Definitions''. In 
contrast,
 If you intend to use a compatibility function in your code it is
 strongly recommended that you check the tests in
 @file{compat-tests.el}.  Alternatively grep the Compat code for
-<UNTESTED> labels.  There you will find the supported calling convention,
-which is guaranteed to work on the supported Emacs versions. We ensure
-this using continuous integration.  If a function is not tested yet in
-@file{compat-tests.el} NO GUARANTEES CAN BE MADE.  You are invited to
-contribute tests in this case
+<UNTESTED> labels.  There you will find the supported calling
+convention, which is guaranteed to work on the supported Emacs
+versions. We ensure this using continuous integration.  FUNCTIONS
+WITHOUT TESTS SHOULD BE CONSIDERED BROKEN.  You are invited to
+contribute missing tests.
 
 It is recommended to subscribe to the
 @uref{https://lists.sr.ht/~pkal/compat-announce, compat-announce}

Reply via email to