Re: Should nil COLLECTION element mean a "nil" candidate forcompleting-read? Alist doc.

[Stefan Monnier]

> I forgot to point out that treating nil this way can lead to extra
> (ugly) code, just to remove or prevent production of such nil entries,
> so they are not available to the user.

A completion table can be a list of strings, a list of conses where the
car is a string, an obarry, a hashtable, or a function.  Your "table" is
none of those, so it's invalid.  Adding (delq nil ...)  before passing
that table to the completion functions doesn't seem like a big issue.

> IOW, I suspect that the number of times where this "feature" might be
> useful (for what?) is less than the number of times where it is
> a nuisance.

It's not a feature.


        Stefan