is it safe to call insert! from different threads? e.g., within a future? I have a way to not need this (e.g., gather data with the future and then insert! from the main thread), I'm more just curious.

@dadair I think that is a sort of tough question

It seems dangerous to assume semantically

I do think that implementation-wise, as long as every thread has fully completed their r/insert! prior to r/fire-rules it may work

That isn’t to say I think it is a supported use-case

So in general, during the “fire rules loop” cycle of the rules engine, the memory is in a mutable state

This is done primarily for performance. The caller perceives the working memory to be a persistent, immutable data structure that is returned after each call to r/fire-rules on a given sesion

However, r/insert! (and a few other similar ones) is called from rule RHS’s. That means it is sort of in that “fire rules loop” part of the lifecycle

yeah that makes sense, I thought as much

accumulators respect saliency?

@souenzzo salience controls when a rule RHS (right-hand side, or consequence in other terms) fires; whether an accumulator is in the rule doesn’t impact it either way. It won’t control the time you actually run the accumulator, though I’m not sure why you’d want to do that.