13:03:24selwynin sec. 5, would prefer more explanation on why the block compilation provisions are not met
13:04:11selwynas well as why you didn´t touch the assembler routines much? lack of time or infeasible? you explain at the end of sec. 5 that it is a lot of work but it would be nice to have that comment earlier
13:05:17selwynfeel that in sec. 6 a discussion on the prospects of actually getting a new gc for sbcl would be nice, and what that might look like. alternatively that could go in the conclusion
13:05:23selwyni would miss out the first paragraph of the conclusion
13:07:07selwyni would think about laying out the structure of the paper in the introduction, sth like ´we will discuss clos, the condition system, optimisation and gc´
13:07:26selwynbut seeing as how all the sections are disjoint from each other you can probably get away with not doing that
13:13:25Colleenfig1 "indicates a call to (call-next-method)" text is too small IMO
13:13:25SAL9000fig1 "indicates a call to (call-next-method)" text is too small IMO
13:14:11Colleensame goes for "are called in..." -- you could omit the "are called in" prefix to make them shorter, and thus raise font size while still fitting inside the box?
13:14:11SAL9000same goes for "are called in..." -- you could omit the "are called in" prefix to make them shorter, and thus raise font size while still fitting inside the box?