Discussion
Why do some implementations omit the occurs check?
Answer: B
Testing every binding for occurrence adds cost to the innermost operation of the system, and programs that would trigger it are uncommon, so many implementations trade soundness for speed while providing a sound unification predicate for those who need it. Implementability is not the obstacle, completeness is unaffected, and standards permit both. A known unsoundness accepted deliberately, with an escape hatch provided, is a defensible engineering position provided it is documented.
No comment is present. Be the first to comment.
Loading…
Post your comment
Please log in or register to post a comment.
Examination Categories
- SSC Exams
- Banking Exams
- Teaching Exams
- Civil Services Exams
- Railways Exams
- Engineering Recruitment Exams
- Defence Exams
- State Government Exams
- Police Exams
- Insurance Exams
- Nursing Exams
- Other Government Exams
- NRA CET
- PG Entrance Exams
- Campus Placement
- MBA Entrance Exams
- CUET and UG Entrance
- Judiciary Exams
- Regulatory Body Exams
- Software Development