; Improve comment from last change

(cherry picked from commit f5451b6a0668f4dc9992562b62ed37a199f1fdad)

diff --git a/lisp/subr.el b/lisp/subr.el
index c114cc45426c97a431cb6cdab6f2a7e51916cdf6..acb566ed42de285904eb91b08caae32f8ec1578d 100644 (file)
--- a/lisp/subr.el
+++ b/lisp/subr.el
@@ -2659,8 +2659,9 @@ are non-nil, then the result is the value of the last binding.
 Some Lisp programmers follow the convention that `and' and `and-let*'
 are for forms evaluated for return value, and `when' and `when-let*' are
 for forms evaluated for side-effect with returned values ignored."
-  ;; Document this convention here because it partially explains why we
-  ;; have both `when-let*' and `and-let*'.
+  ;; ^ Document this convention here because it explains why we have
+  ;;   both `when-let*' and `and-let*' (in addition to the additional
+  ;;   feature of `and-let*' when BODY is empty).
   (declare (indent 1) (debug if-let*))
   (let (res)
     (if varlist