aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorStefan Kangas2023-09-07 23:50:50 +0200
committerStefan Kangas2023-09-07 23:57:20 +0200
commit331dee7e4a8d7b4f0e90de71c71bac58d998cdff (patch)
tree436872a5c5c219b57b41aca9888428d6acead619
parent55c2180d2c34007182edc06b159ca19bd1b584bf (diff)
downloademacs-331dee7e4a8d7b4f0e90de71c71bac58d998cdff.tar.gz
emacs-331dee7e4a8d7b4f0e90de71c71bac58d998cdff.zip
Add note regarding `seq` on GNU ELPA
* lisp/emacs-lisp/seq.el: Add note regarding seq on GNU ELPA. Co-authored-by: Stefan Monnier <monnier@iro.umontreal.ca>
-rw-r--r--lisp/emacs-lisp/seq.el13
1 files changed, 8 insertions, 5 deletions
diff --git a/lisp/emacs-lisp/seq.el b/lisp/emacs-lisp/seq.el
index 6917c541f2e..2a229f71d38 100644
--- a/lisp/emacs-lisp/seq.el
+++ b/lisp/emacs-lisp/seq.el
@@ -38,9 +38,6 @@
38;; the sequence as their second argument. All other functions take 38;; the sequence as their second argument. All other functions take
39;; the sequence as their first argument. 39;; the sequence as their first argument.
40;; 40;;
41;; While seq.el version 1.8 is in GNU ELPA for convenience, seq.el
42;; version 2.0 requires Emacs>=25.1.
43;;
44;; seq.el can be extended to support new type of sequences. Here are 41;; seq.el can be extended to support new type of sequences. Here are
45;; the generic functions that must be implemented by new seq types: 42;; the generic functions that must be implemented by new seq types:
46;; - `seq-elt' 43;; - `seq-elt'
@@ -51,11 +48,17 @@
51;; - `seq-into-sequence' 48;; - `seq-into-sequence'
52;; - `seq-copy' 49;; - `seq-copy'
53;; - `seq-into' 50;; - `seq-into'
54;;
55;; All functions are tested in test/lisp/emacs-lisp/seq-tests.el
56 51
57;;; Code: 52;;; Code:
58 53
54;; Note regarding the `seq' package on GNU ELPA:
55;;
56;; It was decided not to bother upgrading seq beyond 2.24 on GNU ELPA.
57;; The main purpose of the GNU ELPA package was to encourage adoption
58;; and accommodate changes more easily, but it's mature enough that
59;; changes are fairly slow. Thus, we can now rely on "the usual"
60;; solutions to deal with compatibility issues. (Bug#60990)
61
59(eval-when-compile (require 'cl-generic)) 62(eval-when-compile (require 'cl-generic))
60 63
61;; We used to use some sequence functions from cl-lib, but this 64;; We used to use some sequence functions from cl-lib, but this