Closed sjl closed 7 years ago
Fixes https://github.com/HiTECNOLOGYs/cl-charms/issues/34
This is a little verbose. An alternative would be to make a defun-window macro to hide the resolving, but I'm not sure I like that magicness.
defun-window
Something else to consider: instead of a simple if, we could implement resolve-window like this:
if
resolve-window
(defun resolve-window (window-designator) (etypecase window-designator ((eql t) *standard-window*) (window window-designator)))
This would give a nicer error message if a user passes in something that's not either a window or t, but would be a bit more expensive in every single call. I have no strong feelings either way.
t
Fixes https://github.com/HiTECNOLOGYs/cl-charms/issues/34
This is a little verbose. An alternative would be to make a
defun-window
macro to hide the resolving, but I'm not sure I like that magicness.Something else to consider: instead of a simple
if
, we could implementresolve-window
like this:This would give a nicer error message if a user passes in something that's not either a window or
t
, but would be a bit more expensive in every single call. I have no strong feelings either way.