@neauoire some of the other components of the language, specifically its use of content-hashes to refer to subroutines, create the environment for this to work. there's also a notion of a single "symbol library" where all of your compiled routines live, and which can be accessed both at writing/compile time and runtime (right now managed by the VM environment, but ultimately hoping to have it live in the VM as a bootstrapping "OS")
@jakintosh Oh! of course XD *slaps forehead* the definitions are accessible through the symbols! So you're planning on making it possible to do remote API calls between Co environments right?