Hooks about ergo HOT 4 CLOSED

Hooks should be defined in libraries, who are then responsible for invoking the hook at the opportune time.

from ergo.

Waiting on #48

from ergo.

Hooks should be defined in libraries, who are then responsible for invoking the hook at the opportune time.

Not really. As it turns out, hooks are essentially like dynamic predicates that can be called from both C# and Ergo. So the solution was to add the boilerplate to do so from C#. Ergo can already call Ergo code, so there's no need to do anything on that front except maybe add a few helpers to see if a predicate or hook is defined to begin with.

from ergo.

An interesting note is that the current macro expansion system seems to be more powerful than SWI's expand_term/2 and expand_goal/2 hooks. Both implementations are executed at load-time, not impacting runtime performance, but Ergo's is also capable of replacing e.g. arguments in complex terms with a variable that is assigned to the result of the expansion. The expansion is then inserted whole in the body of the predicate where it appears.

from ergo.