Picat Logic Programming and Unification Questions and Answers

Question 1

In Picat, what is the fundamental difference between pattern matching in rule heads and explicit unification using the '=' operator in the rule body?

Accepted Answer

Pattern matching in rule heads is a one-sided unification that does not bind variables in the call, whereas '=' performs full unification.

Answer

Pattern matching is bidirectional, while explicit unification is unidirectional.

Answer

There is no difference; they are syntactically different but semantically identical.

Answer

Pattern matching can only be used with structures, while explicit unification works with all data types.

Question 2

What will be the result of the following Picat query?

`go =>
  X = 1,
  Y = X,
  $f(X, 2) = $f(1, Y),
  println(X),
  println(Y).`

Accepted Answer

It will print 1 and then 1.

Answer

The query will fail because Y is not instantiated in the unification.

Answer

It will print 1 and then a variable.

Answer

The query will fail because X cannot be unified with 1.

Question 3

Which of the following statements correctly describes unification in Picat?

Accepted Answer

Unification is the process of finding a substitution of variables that makes two terms identical, and it can fail if no such substitution exists.

Answer

Unification always succeeds, and if terms cannot be made equal, it throws an exception.

Answer

Picat does not support explicit unification, relying solely on pattern matching in rule heads.

Answer

The unification operator `=` is only used for arithmetic equality, not for structures or lists.

Question 4

Consider the following Picat code:

`process_data($point(A, B), Result) => Result = A + B.
process_data([H|_], Result) => Result = H.`

What happens when the query `process_data(Data, R)` is called if `Data` is the structure `$point(5, 10)`?

Accepted Answer

The first rule is chosen through pattern matching, and R is unified with 15.

Answer

The second rule is chosen, and R becomes 5.

Answer

The query fails because `$point` is not a list.

Answer

Both rules match, leading to a compilation error.

Question 5

Given the goal `[A, B | C] = [x, y, z, w]`, which set of bindings for the variables A, B, and C is correct after successful unification in Picat?

Accepted Answer

A = x, B = y, C = [z, w]

Answer

A = x, B = y, C = z

Answer

A = x, B = [y], C = [z, w]

Answer

Unification fails because the list lengths do not match.

Question 6

Why does Picat distinguish between pattern matching in rule heads and explicit unification (`=`), a feature that makes it different from traditional Prolog?

Accepted Answer

To improve performance and scalability by facilitating better indexing of rules, as pattern matching is simpler than full unification.

Answer

To enforce a functional programming style where rule heads cannot modify arguments.

Answer

To eliminate the need for the occurs check, which is computationally expensive.

Answer

To allow for overloading of the `=` operator for different data types.