-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathreviews.txt
64 lines (42 loc) · 3.11 KB
/
reviews.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
----------------------- REVIEW 1 ---------------------
PC MEMBER:
OVERALL RATING: 3 (strong accept)
REVIEWER'S CONFIDENCE: 3 (high)
This abstract describes the implementation of a data structure library
using an "interface-passing" style, where an interface object is
passed around as a first-class object to computations.
Proposal and case study of a programming style that is novel to the Common Lisp community is clearly relevant to ILC, and should be interesting to attendees.
The abstract is quite intriguing -- I'm looking forward to reading the full paper and trying out the library.
----------------------- REVIEW 2 ---------------------
PC MEMBER:
OVERALL RATING: -2 (reject)
REVIEWER'S CONFIDENCE: 4 (expert)
I have voted to reject this paper for these reasons:
- It inadequately prepares the reader for interface-passing style.
- It does not show how interface passing "bridges the gap" between parametric and ad-hoc polymorphism.
- It does not show the advantages of using interface passing.
Interface passing style is not a well-known technique in the community. A short description of what this entails would be helpful. The example of (insert <alist> person ’name "Rideau")
is simply not illustrative enough.
Why do some object systems use parametric polymorphism and others ad-hoc? Are they commensurate? What would parametric polymorphism look like in Lisp? Why is this a preferred way of writing code?
What improves when parametric polymorphism is added? What degrades? Why would I use technique? How would I know when to use it?
Thank you for taking the time to write and submit your paper.
----------------------- REVIEW 3 ---------------------
PC MEMBER:
OVERALL RATING: 2 (accept)
REVIEWER'S CONFIDENCE: 4 (expert)
The paper describes a library (named LIL) that brings parametric polymorphism into Common-Lisp. The key technology called interface-passing style enables explicit checking of types (or type signatures). As a result, the library provides safer (type based) composition of components than the traditional duck typing.
The author should give technical details of interface-passing style and some (non trivial) examples. The reviewer thinks it is possible because the author already has enough materials in his Github repository and his weblog referred in the paper.
----------------------- REVIEW 4 ---------------------
PAPER: 11
TITLE: LIL: higher-order datastructures meet CLOS
AUTHORS: Francois-Rene Rideau
PC MEMBER:
REVIEWER:
OVERALL RATING: 2 (accept)
REVIEWER'S CONFIDENCE: 2 (medium)
This paper describes an algorithmic data structure library - a means of adding parametric polymorphism using CLOS and an interface-passing style.
The paper is interesting and generally well-written.
In Sec 3.2, Okasaki is mentioned, but does not appear in the references.
TBD is mentioned several times. It would be better if this information was described in a future work section.
The conclusion contains a good discussion of the strengths and weaknesses of the library.
I suggest modifications to the paper to remove or relocate all the TBD statements. Expand more on the novelty mentioned in the conclusion.