You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In SBCL 1.2.11-1 (Fedora), with Quicklisp, symbols generated by LA-MATRIX-TYPE function in runtime (i.e. when a native Lisp array is created by a client) aren't being interned properly. They leak into CL-USER package (or whatever the client's package is), of course cannot be resolved, and debugger pops up.
What it means, it's that you can't use Common Lisp matrices at all. The compiler can't create them.
I fixed it for myself (in my fork) by adding the package prefix to the symbols manually (= with a wrapper function). Not sure why it worked earlier though. If some compilers do add proper package prefixes automatically, this solution may break the code on them.
The text was updated successfully, but these errors were encountered:
In SBCL 1.2.11-1 (Fedora), with Quicklisp, symbols generated by LA-MATRIX-TYPE function in runtime (i.e. when a native Lisp array is created by a client) aren't being interned properly. They leak into CL-USER package (or whatever the client's package is), of course cannot be resolved, and debugger pops up.
What it means, it's that you can't use Common Lisp matrices at all. The compiler can't create them.
I fixed it for myself (in my fork) by adding the package prefix to the symbols manually (= with a wrapper function). Not sure why it worked earlier though. If some compilers do add proper package prefixes automatically, this solution may break the code on them.
The text was updated successfully, but these errors were encountered: