Should we add Revise.jl

[Azzaare]

Should we add Revise.jl to have update in the boat without restarting it, at least during the dev phase?

It might still be buggy though, but if use in sync with tmux, it should be okay. What do you all think?

[tk3369]

Actually, I couldn't get it to work even when I run it locally. It seems that Revise requires some kind of trigger. Normally I would go to the REPL and make a call to the function that I just changed but this is a running process so it's different. It would be nice if you can get it work first.

[rapus95]

The manual trigger we need to put into a callback is Revise.revise(). We could just add !revise as a bot command. That most probably would be both, a lot easier than putting it into some Discord.jl-internal routines and at the same time less of a performance hit because we don't run it all times but only on request. We might even restrict its usage to mods. The only other point we need to take into account is that we might have to switch some ordinary function calls with invokelatest calls. Like there: timholy/Revise.jl#194

[rapus95]

Due to the way how the handlers are called in Discord.jl (via call operator on array/dict elements) we don't even need invokelatest. Just a Revise.revise() AFAIU

[rapus95]

so it might be as easy as

function commander(c::Client, m::Message, ::Val{:revise})
    Revise.revise()
end