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
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