Loading and unloading code currently uses GHC's built-in runtime linker, although in principle, we could use the system dynamic linker. That they could use the

Loading and unloading code currently uses GHC's built-in runtime linker, although in principle, we could use the system dynamic linker. That they could use the system dynamic linker makes me think they're using some form of relatively basic dlopen/dlsym/call-method procedure, or something along those lines. That's fine, though the use of "hotswapping" evokes the image of some more elaborate DSU mechanism.