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

Investigate shared libraries as a path to hot code loading #8

Open
venantius opened this issue Feb 17, 2016 · 1 comment
Open

Investigate shared libraries as a path to hot code loading #8

venantius opened this issue Feb 17, 2016 · 1 comment

Comments

@venantius
Copy link
Owner

The design of Glojure as a language is such that hot code loading and reloading will be enabled by default, since all vars sit in a centrally managed map and can by dynamically re-bound at will depending on compiler scope.

That having been said, runtime imports of Go packages will not be possible by default without deliberately linking all the relevant packages together at compile-time.

I'm still learning about how this has worked in the past and how the limitations are changing in the future, but one thing that is clear is that they are changing. Further (lengthy) reading is available here: https://docs.google.com/document/d/1nr-TQHw_er6GOQRsF6T43GGhFDelrAP0NqSS_00RgZQ/edit?pli=1

@venantius
Copy link
Owner Author

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