The full syntax of a rule is: ( Head :- [Guard | ] Body )
Guard must be a multiset of type constraints of the form: &math(p(\$p_{1}, \ldots , \$p_{n}));. The same abbreviation scheme as defined for atoms applies to type constraints when a process context name $pi occurs exactly two times in the rule.
Type constraints put constraints on the shapes of processes with which the process contexts specified in the arguments can match. The type constraint name p specifies the content of the constraints.
For example, the following type constraints can be used in Guard:
-$p < $q specifies that $p and $q are integer atoms such that the value of $p is less than that of $q.
-$r = $p +. $q specifies that $p, $q, and $r are floating point number atoms such that the sum of the values of $p and $q is equal to the value of $r.
In reality, each type constraint name (such as int or <) has its own mode of usage that specifies which of its arguments are input arguments. The effect of the constraint specified by a type constraint is enabled only after the shapes of its input arguments are all determined.
A process context name $p constrained in Guard is said to be typed in that rule. As a syntactic sugar, typed process context names can be written as link names as follows:
Currently, the following type constraints can be used in the gua