logic-programming

With oso 0.11.1 and Rust client code.

When tracking down policy logic failures using the POLAR_LOG=1 environment variable I will see the logging of the execution of all of my inline queries. The problem is that I have lots of these, but usually I'm not interested in the ones in my core policy files which are fairly static and unchanging, but rather I'm interested in those policy sources that

Hi,

%%logica Engineers

@Engine("sqlite");

Employee(name: "Alice", role: "Product Manager");
Employee(name: "Bob", role: "Engineer");
Employee(name: "Caroline", role: "Engineer");
Employee(name: "David", role: "Data Scientist");
Employee(name: "Eve", role: "Data Scientist");

Engineers(..r) :- Employee(..r), r.role == "Engineer";  # <====== This fails
# Engineers(name:, role:) :-

unsafeOffset :: Int -> Array.Array a -> Array.Array a

and

unsafeCut :: Int -> Array.Array a -> Array.Array a

or,

unsafeSlice :: Int -> Int -> Array.Array a -> Array.Array a

@harendra-kumar Thoughts?

Per discussion in #2743 this class is mis-named.

Also, rename LinkStreamValue to just plain LinkStream.

Hi there,

Thanks for this amazing module.

I think there is a problem with the way terms are printed.
I run some Prolog code from Python, querying Prolog with:

H = pyswip.Variable()
induce = pyswip.Functor('induce', 1)
q = Query(induce(H))
q.nextSolution()
print(H.value)

I get a result like this for H:

[Functor(319757,2,
 [Functor(9048461,3,_10560234,_10560236,_1056023