You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the non-serialization path the :get-alphas-fn is created in the compiler. [1, 2] When clara.rules.engine/assemble is called it expects a user-provided get-alphas-fn to be wrapped already. [3] The durability namespace calls through to the wrapper functionality when it uses the default get-alphas-fn [4, 5] but it does not wrap a user-provider get-alphas-fn. The user would need to use the private create-get-alphas-fn in the compiler to provide a working custom get-alphas-fn. Otherwise Clara would call a user-provided function directly expecting it to return alpha nodes, which it wouldn't do. The way Clara uses the user-provided function to create a get-alphas-fn is an internal implementation detail that should not be exposed in this way.
In the non-serialization path the :get-alphas-fn is created in the compiler. [1, 2] When clara.rules.engine/assemble is called it expects a user-provided get-alphas-fn to be wrapped already. [3] The durability namespace calls through to the wrapper functionality when it uses the default get-alphas-fn [4, 5] but it does not wrap a user-provider get-alphas-fn. The user would need to use the private create-get-alphas-fn in the compiler to provide a working custom get-alphas-fn. Otherwise Clara would call a user-provided function directly expecting it to return alpha nodes, which it wouldn't do. The way Clara uses the user-provided function to create a get-alphas-fn is an internal implementation detail that should not be exposed in this way.
The text was updated successfully, but these errors were encountered: