sb-ext:muffle-conditions declaration does not affect declaim ftype

Bug #2093213 reported by Andrew Kravchuk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
New
Undecided
Unassigned

Bug Description

Consider the following code:

(declaim (sb-ext:muffle-conditions sb-kernel:ftype-proclamation-mismatch-warning))
(declaim (ftype (function (t)) ttt))
(declaim (ftype (function (fixnum)) ttt))

I'd expect the first declaration to silence warnings from the rest, but both running the code in REPL and calling COMPILE-FILE on the file containing it produces the warning

; caught STYLE-WARNING:
; The new FTYPE proclamation for COMMON-LISP-USER::TTT
; (FUNCTION (FIXNUM))
; does not match the old FTYPE proclamation
; (FUNCTION (T) *)

Is it something I'm missing regarding sb-ext:muffle-conditions?..

I'm using SBCL 2.5.0 on Linux.

Revision history for this message
Stas Boukarev (stassats) wrote :

muffle-conditions is compile-time only.

Revision history for this message
Andrew Kravchuk (awkravchuk) wrote :

Ah, got it, thanks.

Revision history for this message
Tomas Hlavaty (tomas-hlavaty) wrote : Re: [Bug 2093213] Re: sb-ext:muffle-conditions declaration does not affect declaim ftype

On Tue 07 Jan 2025 at 19:47, Stas Boukarev <email address hidden> wrote:
> muffle-conditions is compile-time only.

could you elaborate?

during compile-file is compile-time, isn't it?

and when both sb-eval and sb-fasteval are off,
repl input is compiled and thus also compile-time, isn't it?

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.