diff options
author | Stefan Kangas <stefankangas@gmail.com> | 2025-03-05 03:36:04 +0100 |
---|---|---|
committer | Stefan Kangas <stefankangas@gmail.com> | 2025-03-05 03:41:49 +0100 |
commit | 7ba62284137ba162df16f55c75bda4d56da7dfe7 (patch) | |
tree | 1006ec88ec1edb4488198c624fd6b266b82d7c65 /lisp/emacs-lisp | |
parent | 8c8ff13e7bdaab1446873d3401fe1a53a827198d (diff) | |
download | emacs-7ba62284137ba162df16f55c75bda4d56da7dfe7.tar.gz emacs-7ba62284137ba162df16f55c75bda4d56da7dfe7.tar.bz2 emacs-7ba62284137ba162df16f55c75bda4d56da7dfe7.zip |
Make byte-compile-cond-use-jump-table obsolete
This user option was introduced in 2017, with the rationale:
"This is a workaround for when `byte-compile-cond-jump-table'
accidentally generates wrong code (hasn't happened so far in my
tests), and should be removed once we're sure there are no issues
with it." https://lists.gnu.org/r/emacs-devel/2017-02/msg00223.html
There hasn't been any bugs in this area within the last 6 years, and the
few we did see before that were quickly resolved. Let's declare this
variable obsolete now, while keeping its behavior when set to nil. We
can always revert the obsoletion if it turns out to be needed after all.
* lisp/emacs-lisp/bytecomp.el
(byte-compile-cond-use-jump-table): Declare obsolete.
Diffstat (limited to 'lisp/emacs-lisp')
-rw-r--r-- | lisp/emacs-lisp/bytecomp.el | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/lisp/emacs-lisp/bytecomp.el b/lisp/emacs-lisp/bytecomp.el index 66407774007..1807f8674fb 100644 --- a/lisp/emacs-lisp/bytecomp.el +++ b/lisp/emacs-lisp/bytecomp.el @@ -242,6 +242,7 @@ This includes variable references and calls to functions such as `car'." "Compile `cond' clauses to a jump table implementation (using a hash-table)." :version "26.1" :type 'boolean) +(make-obsolete-variable 'byte-compile-cond-use-jump-table nil "31.1") (defvar byte-compile-dynamic nil "Formerly used to compile function bodies so they load lazily. |