master 543b8717c7: ; Add commentary to comp-tests.el

[Eli Zaretskii]

branch: master
commit 543b8717c7b4d82e2e0afdfe339be1d6bfdf5c97
Author: Eli Zaretskii <eliz@gnu.org>
Commit: Eli Zaretskii <eliz@gnu.org>

    ; 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)
---
 test/src/comp-tests.el | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/test/src/comp-tests.el b/test/src/comp-tests.el
index a400a1a50a..1edbd1777c 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)