Overly liberal with * in some type specifiers

Bug #1860919 reported by Douglas Katzman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Fix Released
Undecided
Unassigned

Bug Description

example 1.
(compile nil '(lambda (x) (the * x))) => #<FUNCTION>, NIL, NIL

example 2.
(compile nil '(lambda (f) (funcall (the (function (*) boolean) f) 1))) => #<FUNCTION>, NIL, NIL

but
(compile nil '(lambda (x) (declare (* x)) x)) => #<FUNCTION>, T, T ; correct answer

"*" should only be legal in compound FUNCTION specifier if ARG-TYPESPEC is omitted and VALUE-TYPESPEC is present in the metasyntax "function [arg-typespec [value-typespec]]"

Douglas Katzman (dougk)
Changed in sbcl:
status: New → Fix Committed
Stas Boukarev (stassats)
Changed in sbcl:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.