Uncaught macro expansion errors in first argument of various MAP* functions

Bug #1749253 reported by Paul F. Dietz on 2018-02-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Low
Unassigned

Bug Description

(mapc (lambda) nil) ==>

error while parsing arguments to DEFMACRO LAMBDA:
  too few elements in
    ()
  to satisfy lambda list
    (SB-IMPL::ARGS &BODY SB-IMPL::BODY):
  at least 1 expected, but got 0
[...]
  0: (SB-C::CHECK-DS-LIST/&REST #<unavailable argument> #<unavailable argument> #<unavailable argument> #<unavailable argument>)
  1: ((MACRO-FUNCTION LAMBDA) (LAMBDA) #<unused argument>)
  2: ((FLET SB-IMPL::PERFORM-EXPANSION :IN MACROEXPAND-1) #<FUNCTION (MACRO-FUNCTION LAMBDA) {223E863B}> NIL)
  3: (SB-INT:%MACROEXPAND (LAMBDA) #S(SB-KERNEL:LEXENV :FUNS NIL :VARS ((#1=#:G1 . #) (#:G0 . #)) :BLOCKS ((#:G2 # #<SB-C::CTRAN 1 {10069A8F63}> #<SB-C::LVAR 2 {10069A8F93}>)) :TAGS ((#:G3 #2=# #<SB-C::CTR..
  4: (SB-C::IR1-CONVERT-%FUNCALL #<SB-C::CTRAN 5 {10069AAC53}> #<SB-C::CTRAN 6 {10069AADF3}> NIL (SB-C::%FUNCALL (LAMBDA) (CAR #:G1)))
[...]

And similarly for MAPCAN, MAPLIST, MAPCAR, MAPCON, MAPL.

Stas Boukarev (stassats) wrote :

It boils down to
(funcall (lambda))

Changed in sbcl:
status: New → Triaged
importance: Undecided → Low
tags: added: malformed-source
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers