From: Eli Zaretskii <eliz@gnu.org>
Date: Tue, 13 Sep 2022 13:49:02 +0000 (+0300)
Subject: ; Add commentary to comp-tests.el
X-Git-Tag: emacs-29.0.90~1856^2~559
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=543b8717c7b4d82e2e0afdfe339be1d6bfdf5c97;p=emacs.git

; Add commentary to comp-tests.el

Sigh... why do people insist on removing useful comments and leave
their tricky code more obfuscated than it must be??
* test/src/comp-tests.el (comp-tests-type-spec-tests): Add a
comment explaining why the expressions are quoted.  (Bug#51104)
---

diff --git a/test/src/comp-tests.el b/test/src/comp-tests.el
index a400a1a50a1..1edbd1777c6 100644
--- a/test/src/comp-tests.el
+++ b/test/src/comp-tests.el
@@ -860,6 +860,11 @@ Return a list of results."
 
 (cl-eval-when (compile eval load)
   (defconst comp-tests-type-spec-tests
+    ;; Why we quote everything here, you ask?  So that values of
+    ;; `most-positive-fixnum' and `most-negative-fixnum', which can be
+    ;; architecture-dependent, do not end up hardcoded in the
+    ;; resulting byte-compiled file, and thus we could run the same
+    ;; .elc file on several architectures without fear.
     '(
       ;; 1
       ((defun comp-tests-ret-type-spec-f (x)