missing CALL-NEXT-METHOD optimization

Bug #715129 reported by Nikodemus Siivola on 2011-02-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Wishlist
Unassigned

Bug Description

PCL does not detect cases such as

(defmethod foo ((a bar))
  (call-next-method a))

which are equivalent to argument-free call-next-method -- which in turn is faster as it doesn't need to do any validity checking.

1. In many cases the code walker can know this statically.
2. In other cases I suspect %CHECK-CNM-ARGS could start with a quick EQ test.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers