SBCL

Uncaught compiler errors in malformed SPECIAL declarations

Bug #1740756 reported by Paul F. Dietz on 2018-01-01

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	SBCL	Fix Released	Undecided	Unassigned

Bug Description

There are two distinct uncaught errors in malformed SPECIAL declarations.

(compile nil '(lambda () (declare (special 1))))

==>

The value
  1
is not of type
  (OR CONS SYMBOL)
when binding SB-IMPL::NAME
   [Condition of type TYPE-ERROR]
[...]
Backtrace:
  0: (SB-KERNEL:ASSERT-SYMBOL-HOME-PACKAGE-UNLOCKED 1 "declaring ~A special") [more]
  1: (SB-KERNEL:PROGRAM-ASSERT-SYMBOL-HOME-PACKAGE-UNLOCKED :COMPILE 1 "declaring ~A special")
[...]

and also

(compile nil '(lambda () (declare (special (foo)))))

===>

The value
  (FOO)
is not of type
  SYMBOL
when binding SB-C::NAME
   [Condition of type TYPE-ERROR]
[...]
Backtrace:
  0: (SB-C::FIND-IN-BINDINGS NIL (FOO)) [external]
  1: (SB-C::PROCESS-SPECIAL-DECL (SPECIAL (FOO)) #S(SB-KERNEL:LEXENV :FUNS NIL :VARS NIL :BLOCKS NIL :TAGS NIL :TYPE-RESTRICTIONS NIL :LAMBDA NIL ...) NIL T :COMPILE)
[...]