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

Hot-code-reload: can we do it git driven? #360

Open
1 task
goodboy opened this issue Apr 27, 2023 · 0 comments
Open
1 task

Hot-code-reload: can we do it git driven? #360

goodboy opened this issue Apr 27, 2023 · 0 comments

Comments

@goodboy
Copy link
Owner

goodboy commented Apr 27, 2023

This has been on the idea backlog for a long while, obviously in pursuit
of something like what's in erlang's OTP and consequently elixer:


Theoretical


Ideas for a MVP:

Presuming we were to take the same protocol as erlang namely,
https://blog.stenmans.org/theBeamBook/#_hot_code_loading:

In Erlang there is a semantic difference between a local function call
and a remote function call. A remote call, that is a call to
a function in a named module, is guaranteed to go to the latest loaded
version of that module. A local call, an unqualified call to
a function within the same module, is guaranteed to go to the same
version of the code as the caller.

and we wanted reloads to be tracked and triggered by git history
updates, here are some thots on how to scratch at this:


Further related resources from #113:

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