bug#16768: 24.3.50; `quit-restore-window' with KILL=t replaces special-display buffer in its dedicated window

[Drew Adams <drew.adams@oracle.com>]

> > You do not want to reuse such a frame for another buffer,
> > especially for a non special-display buffer.  The frame
> > should be deleted when its buffer is killed.
> 
> What if you have just one frame, and it's dedicated and you
> kill the buffer?

I figured someone might immediately focus on that.  It's a
corner case.  Choose something appropriate.  Not worth
arguing about at the outset.

One possibility: Kill the buffer, then call `delete-frame'.
The latter attempt raises an error, and you end up, at worst,
in the situation that arises today: another buffer in the
special-display frame.  Not appropriate, but a more minor
bug than doing that systematically.

Another possibility: Make killing the buffer and deleting
the frame transactional, i.e., acting together like an atomic
action.  Raise an error before killing the buffer if deleting
the frame afterward would raise an error.

Another possibility: Do like we do for `buffer-quit-function'
or `frame-auto-hide-function': provide an option to let the
user decide.

Propose another possibility, if you like.  And another.

But this should be the last thing to worry about.  Debate it
at the end if there is interest.  It should not sidetrack
fixing the bug, taking it down a rabbit hole to never-never
land.