Fork me on GitHub
Joshua Suskalo15:02:32

I'm currently doing a project with OpenGL, which requires you to be particular about which thread things get run on (namely on linux, you must run all subsequent context-specific commands on the thread which creates a context), and I was curious if there is a way to effectively give the thread I'm doing operations on back to nrepl so that it can process messages on it, and then resume my code's execution, or would it be better for me to just make sure that the code I write happens on a thread other than the repl thread, and that anything context-specific gets sent to a queue to get processed on that thread?


There is a threadpool behind nrepl. I think you could potentially achieve what you desire, but I also think it would be arduous.

Joshua Suskalo21:02:27

Alright, fair enough. I was hoping I could do something like livesupport in slime, but if that's not the case, then that's alright, I can just figure it out with a separate thread.