hmm, I noticed that when using sci/merge-opts, :load-fn get's lost if it's not specified in the merge-opts call, but was wondering if nilling it out should be actually supported

did you provide :load-fn nil or did it do this itself?

didn't provide the key at all

for now, I can pass the load-fn that I passed during sci/init, in the sci/merge-opts call as well

yes, that seems a bug then

PR welcome

yes, got a bit fumbled on supporting nilling it out 🙂

something odd going on, since at sci/merge-opts time, load-fn not found in original env, I'll look into this a bit later with fresh eyeys

original env = mutable atom, which is perhaps the reason?

might be, have to rule out that I'm not doing something silly. Could add a watch after init to trace a bit