Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
When compiling the following:
(declaim (optimize (debug 2) ))
(declaim (ftype (function ((integer 0 100)) (integer 0 100)) test))
(defun test (y)
I get this note printed:
; file: /home/ury/work/note.lisp
; in: DEFUN TEST
; (DEFUN TEST (Y) Y)
; --> PROGN EVAL-WHEN SB-IMPL::%DEFUN CATCH BLOCK SB-C::%WITHIN-CLEANUP
; --> SB-INT:NAMED-LAMBDA
; #'(SB-INT:NAMED-LAMBDA TEST (Y) (BLOCK TEST Y))
; note: type assertion too complex to check:
; (VALUES (MOD 101) &REST T).
; compilation unit finished
; printed 1 note
This happens only at debug levels of 2 or 3; with 0 or 1 it compiles
without any notes.
Not sure if this can be qualified as a bug, but it is certainly very
surprising to see
"type assertion too complex" on such a trivial example.
This is SBCL 188.8.131.52 from cvs, Debian(testing)/x86
Sidney Markowitz <sidney@...> writes:
[ please don't follow up to an unrelated post: it breaks threading in
my mailreader. Instead, please compose a fresh message to the
mailing list address. ]
> In the current CVS, the file
> class-sb-gray-fundamental-input-stream.texinfo is included in
> /doc/manual/streams.texinfo but the file does not exist, breaking the
> build of the documentation.
The file you refer to is a generated file. Try "make clean" followed
by "make" in the doc/manual/ directory.