Swank-fancy-inspector patch

Douglas Katzman <[email protected]>
Newsgroups gmane.lisp.steel-bank.devel,gmane.lisp.slime.devel
Message-ID <CAOrNasw79rpd5dVWNdDe0ZhT6=cGToFWN4D3+g28BNkbbH9Mvg@mail.gmail.com>
The patch inlined below fixes the display of DEFTYPE lambda lists.

It's compatible enough with older SBCL - extracting the expander's arglist
is just a gensym, not technically wrong but not as useful as the
destructuring lambda list.
While this could be considered a regression, I don't think it needs
conditionalizing on SBCL release. The way to do so, in theory, is check
whether (:type :lambda-list) is a kind of info by asking for meta-info ...
except that it won't actually fix anything because current SBCL reports
that (:type :lambda-list) exists, but it never has data.

--- swank-fancy-inspector.lisp~ 2015-04-30 23:24:08.000000000 -0400
+++ swank-fancy-inspector.lisp 2015-04-30 23:34:31.000000000 -0400
@@ -119,10 +119,7 @@
        (unless (eq t fun)
          (append
           `("Type-specifier lambda-list: "
-            ,(inspector-princ
-              (if (eq :primitive kind)
-                  (arglist fun)
-                  (sb-int:info :type :lambda-list symbol)))
+            ,(inspector-princ (arglist fun))
             (:newline))
           (multiple-value-bind (expansion ok)
               (handler-case (sb-ext:typexpand-1 symbol)

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y

_______________________________________________
Sbcl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sbcl-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.