Re: the ...-unload-hook convention doesn't work

[Luc Teirlinck]

I can not but wonder what we exactly want to achieve with `unload-feature'.
Is there any hope of ever making it safe enough to be called in an
actual editing session in which non-trivial work is invested and will
_continue_ to be invested after unloading a feature?  I do not believe
that it currently comes even remotely close to that standard.

The worst thing is that even reloading the feature often can not undo
the damage:

ELISP> (fboundp 'macroexpand)
t
ELISP> (require 'cl)
cl
ELISP> (fboundp 'macroexpand)
t
ELISP> (unload-feature 'cl) ;; Long output flushed
ELISP> (require 'cl)
cl
ELISP> (fboundp 'macroexpand)
nil
ELISP> 

Sincerely,

Luc.