So you want to live-reload Rust (2020)

Re:So you want to live-reload Rust (2020) by throwaway81523 on Wednesday October 13, 2021 @11:50PM (#28860319)

This is about reloading dynlibs, technically cool I guess, but maybe asking for trouble. I prefer to launch a new process, then transfer any open connections and fd's with the SCM_RIGHTS auxiliary message under Linux.

I once asked Joe Armstrong (RIP) about Erlang's famous hot reload feature compared to doing something like that, and he agreed with me that hot reload wasn't really worthwhile, as sexy as it might sound.

[ Parent | on HN ]

Re:So you want to live-reload Rust (2020) by rogual on Thursday October 14, 2021 @07:18AM (#28862840)

Nice. New process definitely sounds cleaner if it supports what your program does, but I think if you have open GUI windows or GPU contexts you want to keep around, the dylib route might be your only option.

[ Parent | on HN ]

Re:So you want to live-reload Rust (2020) by throwaway81523 on Thursday October 14, 2021 @06:20PM (#28870965)

I don't know about GPU contexts: is there no way to hand them off? Reliable hot reload is always painful no matter how you do it. I don't know the situation with gpu contexts but if your long running program needs hot reloads and has a gui, maybe you want to split the gui itself into a separate process, or alternatively maybe do that with the component requiring reload.

[ Parent | on HN ]