summaryrefslogtreecommitdiff
path: root/tests/mop-27.impure.lisp
blob: f0673aa4b033cdceb2a783a7386c41ef00eef5f8 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
;;;; miscellaneous side-effectful tests of the MOP

;;;; This software is part of the SBCL system. See the README file for
;;;; more information.
;;;;
;;;; While most of SBCL is derived from the CMU CL system, the test
;;;; files (like this one) were written from scratch after the fork
;;;; from CMU CL.
;;;;
;;;; This software is in the public domain and is provided with
;;;; absolutely no warranty. See the COPYING and CREDITS files for
;;;; more information.

;;; a test of a non-standard specializer class.  Some context: a
;;; (mostly content-free) discussion on comp.lang.lisp around
;;; 2007-05-08 about the merits of Lisp, wherein an F#/OCaml advocate
;;; implies roughly "I've heard that CLOS is slower than pattern
;;; matching"

;;; This implements a generic function type which dispatches on
;;; patterns in its methods.  The implementation below is a simple
;;; interpreter of patterns; compiling the patterns into a
;;; discrimination net, or other optimized dispatch structure, would
;;; be an interesting exercise for the reader.  (As would fixing some
;;; other marked issues).

(defclass pattern-specializer (sb-mop:specializer)
  ((pattern :initarg pattern :reader pattern)
   (direct-methods :initform nil :reader specializer-direct-methods)))

(defvar *pattern-specializer-table* (make-hash-table :test 'equal))

(defun ensure-pattern-specializer (pattern)
  (or (gethash pattern *pattern-specializer-table*)
      (setf (gethash pattern *pattern-specializer-table*)
            (make-instance 'pattern-specializer 'pattern pattern))))

;;; only one arg for now
(defclass pattern-gf/1 (standard-generic-function) ()
  (:metaclass sb-mop:funcallable-standard-class))

(defmethod sb-pcl:specializer-type-specifier
    ((proto-generic-function pattern-gf/1)
     (proto-method t)
     (specializer pattern-specializer))
  (labels ((to-type (pattern)
             (cond
               ((null pattern) 't)
               ((atom pattern) `(eql ,pattern))
               (t `(cons ,(to-type (car pattern))
                         ,(to-type (cdr pattern)))))))
    (to-type (pattern specializer))))

(defun matchesp (arg pattern)
  (cond
    ((null pattern) t)
    ((atom pattern) (eql arg pattern))
    (t (and (matchesp (car arg) (car pattern))
            (matchesp (cdr arg) (cdr pattern))))))

(defun method-interpreting-function (methods gf)
  (lambda (arg)
    (dolist (method methods (no-applicable-method gf (list arg)))
      (when (matchesp arg (pattern (first (sb-mop:method-specializers method))))
        (return (funcall (sb-mop:method-function method) (list arg) nil))))))

(defmethod sb-mop:compute-discriminating-function ((generic-function pattern-gf/1))
  (lambda (arg)
    (let* ((methods (sb-mop:generic-function-methods generic-function))
           (function (method-interpreting-function methods generic-function)))
      (sb-mop:set-funcallable-instance-function generic-function function)
      (funcall function arg))))

;;; protocol functions.  SPECIALIZER-DIRECT-METHODS is implemented by
;;; a reader on the specializer.  FIXME: implement
;;; SPECIALIZER-DIRECT-GENERIC-FUNCTIONS.
(defmethod sb-mop:add-direct-method ((specializer pattern-specializer) method)
  (pushnew method (slot-value specializer 'direct-methods)))
(defmethod sb-mop:remove-direct-method ((specializer pattern-specializer) method)
  (setf (slot-value specializer 'direct-methods)
        (remove method (slot-value specializer 'direct-methods))))

(defgeneric simplify (x)
  (:generic-function-class pattern-gf/1))
;;; KLUDGE: order of definition matters, as we simply traverse
;;; generic-function-methods until a pattern matches our argument.
;;; Additionally, we're not doing anything interesting with regard to
;;; destructuring the pattern for use in the method body; a real
;;; implementation would make it more convenient.
(let ((specializer (ensure-pattern-specializer 'nil)))
  (eval `(defmethod simplify ((x ,specializer)) x)))
(let ((specializer (ensure-pattern-specializer '(* nil 0))))
  (eval `(defmethod simplify ((x ,specializer)) 0)))
(let ((specializer (ensure-pattern-specializer '(* 0 nil))))
  (eval `(defmethod simplify ((x ,specializer)) 0)))


(with-test (:name (:mop-27))
  (assert (eql (simplify '(* 0 3)) 0))
  (assert (eql (simplify '(* (+ x y) 0)) 0))
  (assert (equal (simplify '(+ x y)) '(+ x y))))