mirror of
git://git.sv.gnu.org/emacs.git
synced 2026-01-07 04:10:27 -08:00
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.
This commit is contained in:
parent
ceebf3efbe
commit
2b552f3489
2 changed files with 5 additions and 12 deletions
|
|
@ -771,10 +771,7 @@ DEFUN ("fset", Ffset, Sfset, 2, 2, 0,
|
|||
if (AUTOLOADP (function))
|
||||
Fput (symbol, Qautoload, XCDR (function));
|
||||
|
||||
/* Convert to eassert or remove after GC bug is found. In the
|
||||
meantime, check unconditionally, at a slight perf hit. */
|
||||
if (! valid_lisp_object_p (definition))
|
||||
emacs_abort ();
|
||||
eassert (valid_lisp_object_p (definition));
|
||||
|
||||
set_symbol_function (symbol, definition);
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue