Strange behaviour of subtypep with undefined types
Bug #1886808 reported by
Syll
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
With attached code file :
(load "code")
(f)
(with-
=> subtypep signals a style-warning after execution of (with-compilati
(but not while loading/compiling the file, calling (f), nor during execution of f itself)
Discussion on this bug (https:/
----
SBCL 2.0.5
To post a comment you must log in.
Wrapping a compilation unit around code that you're trying to compile causes the compiler to "notice" that code will possibly be compiled suboptimally if you references types that are unknown. worthy, but that's the effect that the compilation unit has.
In your minimal example there is no code that actually causes bad assembly code to be emitted, nor would it necessarily be construed as style-warning-
But *NOT* wrapping a compilation-unit does *not* ask the compiler to notice such things.
For further details see the handler in on-unit ... unknown- type
(lambda (c)
(note-undefined -reference (parse- unknown- type-specifier c)
:type) )))
(defun %with-compilati
(handler-bind ((parse-
You may not desire this behavior, but it is what it is.