Re: setq's with missing final arguments.

[Artur Malabarba]

Alan said:
> In the setq, there is a missing argument after "bar".  At the moment,
the byte compiler just generates code to assign nil to bar, without
giving any warning.  IMAO, this is Very Bad.

Oleh said:
> In my opinion, multi-variable setq should be deprecated altogether.

I'm in favor of giving warnings about any one of these (we shouldn't
actually change any behavior right now, of course).
I agree with Alan that the current behavior (allowing multiple args
where the last one might be assumed to be nil) is bad (regardless of
how consistent it is), and I think both options are a fine way to warn
users.