freenode/#sicl - IRC Chatlog
Search
17:13:24
scymtym
yeah, it will potentially catch fewer cleavir bugs when running in SBCL. but without the exception, it might not run at all
17:14:30
Bike
i think i'll try loading your branch and convincing myself that it's an sbcl problem before merging
17:16:19
scymtym
sure. there is no rush. feel free to not merge now if you want to make certain improvements first
17:32:11
Bike
trucler doesn't seem to have a way to get info about DECLARATION proclamations. that may be a little sticking point
18:10:55
Bike
when i try to load the visualizer i get "Invalid initialization argument: :UPDATE-INSTANCES-ON-REDEFINITION in call for class #<STANDARD-CLASS COMMON-LISP:STANDARD-CLASS>." while loading application.fasl.
18:12:06
Bike
and i think my quicklisp is fully updated. i ran into some problems with that make-ea thing so i wiped the asdf cache entirely to get this far
18:16:17
ebrasca
beach: following your tip of removing pathname-% from (%type :initarg :type :reader pathname-%type) collides wiht funcition type.
18:17:13
scymtym
(it makes the window update when the corresponding code is redefined so users have no use for it)
18:47:33
scymtym
i don't have a proper recipe and i think there might complex preconditions, but when i compile and run everything with (proclaim '(optimize (debug 3) (safety 3) (speed 1) (compilation-speed 0))), just starting the visualizer triggers it
18:48:59
scymtym
i wouldn't be surprised if it also depends on which thread evaluates what and finicky stuff like that
18:52:05
scymtym
i forgot, i have to modify the form to trigger a compilation to make the problem appear
18:54:24
scymtym
Bike: this is the simplest way to reproduce it i could find: https://techfak.de/~jmoringe/sbcl-crash.png
18:55:30
Bike
do you have the proclamations in your sbclrc or something? because that looks like i did and i didn't get a crash
18:56:04
scymtym
as i wrote above, (proclaim '(optimize (debug 3) (safety 3) (speed 1) (compilation-speed 0))), or do you mean something else?
18:57:30
scymtym
in this context, this difference probably is that high safety generates type checks based on slot :TYPE options
4:04:59
beach
ebrasca: You shadow the symbol, and then if you need to refer to the CL symbol in your package, you use the CL: prefix.