Difference between revisions of "Publications/valais.18.seminar"
From LRDE
(Created page with "{{CSIReport | authors = Leo Valais | title = SUBTYPEP: An Implementation of Baker's Algorithm | year = 2018 | number = 1810 | abstract = The Common Lisp language provides a pr...") |
|||
| Line 4: | Line 4: | ||
| year = 2018 |
| year = 2018 |
||
| number = 1810 |
| number = 1810 |
||
| − | | abstract = The Common Lisp language provides a predicate |
+ | | abstract = The Common Lisp language provides a predicate functionSUBTYPEP, for instrospecting sub-type relationship. In some situations, and given the type system of this languageknowing whether a type is a sub-type of another would require enumerating all the element of that type, possibly an infinite number of them. Because of that, SUBTYPEP is allowed to return the two values (NIL NIL), indicating that it couldn't answer the question. Common Lisp implementations have a tendency to frequently not answereven in situations where they could. Such an abusive behavior prevents potential optimizations to occur, or even leads to violating the standard. In his paper entitled “A Decision Procedure for Common Lisp's SUBTYPEP Predicate”Henry Baker proposes an algorithm that he claims to be both more accurate and more efficient than the average SUBTYPEP implementation. In this report, we present a partial implementation of his algorithm, discuss some technical aspects, present some benchmarks and most importantlycompare the accuracy of both implementations. |
| type = techreport |
| type = techreport |
||
| id = valais.18.seminar |
| id = valais.18.seminar |
||
Latest revision as of 15:00, 3 July 2018
- Authors
- Leo Valais
- Type
- techreport
- Year
- 2018
- Number
- 1810
Abstract
The Common Lisp language provides a predicate functionSUBTYPEP, for instrospecting sub-type relationship. In some situations, and given the type system of this languageknowing whether a type is a sub-type of another would require enumerating all the element of that type, possibly an infinite number of them. Because of that, SUBTYPEP is allowed to return the two values (NIL NIL), indicating that it couldn't answer the question. Common Lisp implementations have a tendency to frequently not answereven in situations where they could. Such an abusive behavior prevents potential optimizations to occur, or even leads to violating the standard. In his paper entitled “A Decision Procedure for Common Lisp's SUBTYPEP Predicate”Henry Baker proposes an algorithm that he claims to be both more accurate and more efficient than the average SUBTYPEP implementation. In this report, we present a partial implementation of his algorithm, discuss some technical aspects, present some benchmarks and most importantlycompare the accuracy of both implementations.