Checking of given type definitions and predicate declarations

Collection of different examples with results:

• No test data <1>
• File is empty <1.1>
• File does not exist <1.2>
• Subtype relationship <2>
• Subtype relationship between undefined types <2.1>
• Subtype relationship with a type alias <2.2>
• Subtype relationship between types with different type parameter sequences <2.3>
• Avoiding cycles in subtype relationships <2.4>
• Type equivalence <3>
• Use of a unknown type in a type definition by type equivalence <3.1>
• Same type equivalence is given several times in one module <3.2>
• Type equivalence between types with different type parameter sequences <3.3>
• Transitive interpretation of type equivalences <3.4>
• Avoiding cycles in type equivalences <3.5>
• Type definition <4>
  • Type definition with no different type parameters <4.1>
  • Uncompleted type definition <4.2>
  • Type definitions of a type with different type constructors <4.3>
  • Type definitions of a type with different type aliases <4.4>
  • Different type definitions of a type with type constructor and type alias <4.5 and 4.6>
  • Several mentions of a type definition in a module <4.7>
  • Conflict between a normal and a abstract type definition in a file containing no
  • Section borders <4.8>
• Predicate declaration <5>
• Predicate declaration with different type arguments <5.1>
• Uncompleted predicate declaration <5.2>
• Several mentions of a predicate declaration in a module <5.3>
• Internal used type symbols <6>
• Forbidden use of internal type bottom in type definition, subtype relationship, type equivalence or predicate declaration <6.1>
• Forbidden use of internal type top in type definition <6.2>
• Allowed use of internal type top <6.3>
• Special error messages during the type inference <7>
• Not declared predicate is used in clause <7.1>
• Not declared function is used in clause (functions are declared by type definitions) <7.2>

File test_input.pl

PREV: Case-study: container

NEXT: Module system