summaryrefslogtreecommitdiff
path: root/lisp/emacs-lisp/check-declare.el
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2019-08-21 22:19:03 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2019-08-21 22:30:18 -0700
commit2b552f34892ee3c73f4b5fb5380218dc6ebbf4bb (patch)
treea5c875fa6082cb43b403a9bfa0b3ef2b90d93ebc /lisp/emacs-lisp/check-declare.el
parentceebf3efbea7faffc01558d88c91250539c737e0 (diff)
downloademacs-2b552f34892ee3c73f4b5fb5380218dc6ebbf4bb.tar.gz
emacs-2b552f34892ee3c73f4b5fb5380218dc6ebbf4bb.tar.bz2
emacs-2b552f34892ee3c73f4b5fb5380218dc6ebbf4bb.zip
Don’t debug fset by default
This GC bug seems to have been fixed, so the check is no longer needed in production code. From a suggestion by Pip Cet in: https://lists.gnu.org/r/emacs-devel/2019-08/msg00316.html * src/alloc.c (SUSPICIOUS_OBJECT_CHECKING) [!ENABLE_CHECKING]: Do not define. (find_suspicious_object_in_range, detect_suspicious_free): Expand to proper dummy expressions if !SUSPICIOUS_OBJECT_CHECKING. * src/data.c (Ffset): Convert test to an eassert.
Diffstat (limited to 'lisp/emacs-lisp/check-declare.el')
0 files changed, 0 insertions, 0 deletions