Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What are the pitfalls of reloading? #57

Open
psionic-k opened this issue Jul 4, 2024 · 0 comments
Open

What are the pitfalls of reloading? #57

psionic-k opened this issue Jul 4, 2024 · 0 comments

Comments

@psionic-k
Copy link

psionic-k commented Jul 4, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant