Skip to content

What are the pitfalls of reloading? #57

@psionic-k

Description

@psionic-k

I can't reconcile what was said on the mailing list about unloading leaving old functions laying around. The reloading here just loads the new module without unloading the old one, correct?

Perhaps the old module just needs to move itself out of the way and then call a closure that loads the new module, which can then patch itself in. This wouldn't require a shim module.

It seems the bash script integration can be done just as well from Elisp, without a script.

Edit: Issue mentioned in reloading was closed, though nobody linked to the details of what "fixed on MacOS" means

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions