Fork me on GitHub
#cider
<
2019-11-05
>
bozhidar06:11:59

@deas Never tried to AOT compile it. I think it’d be best to file a ticket, so we can discuss this further. Unfortunately the delayed handling has been a bit brittle due to some race conditions in Clojure’s require. Potentially using some form of serializing require would fix the problem there.

deas10:11:14

@bozhidar I hope you don't mind me borrowing a bit of cider-nrepl boilerplate. 😉

bozhidar10:11:30

Not at all. 🙂

👍 1
tomd10:11:56

Can anyone help with this please?

bozhidar11:11:46

@tomd I meant to reply yesterday, but I totally forgot to do this. It’d be best to file a ticket, so I won’t forget to debug what exactly is going on there. Generally the REPL to use is selected based on the type of the underlying source buffer, not on what you used last. Recency is only a factor if you have several REPLs of the same type (e.g. clj) in the same session.

tomd17:11:36

Thanks @bozhidar. I'll file a ticket when I next get the chance.

tomd09:11:49

@bozhidar fyi the docs state "Ambiguous situations could arise when, for instance... ...the current buffer is a cljc buffer and both clj and cljs REPLs exist in the session. In such cases the current REPL is the most recently viewed REPL of the relevant type." Which is consistent with what I've seen. I submitted a GitHub issue asking that *cider-scratch* behaviour be made consistent with that of a cljc buffer in such a situation.