bug#45333: complex command history should not save optional nil parameters

[Michael Heerdegen]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
> > Anyway, trying of prettify away those `nil`s seems like overkill to me.
> > In theory even an optional `nil' can be significant.
>
> They can be if the signature is a &rest that parses the parameters by
> hand, but are there other cases where a nil optional argument is
> significant?

`cl-defun's?  Also advises have access to the actually passed parameter
list.  Dunno if there are other cases.

Michael.