libera/commonlisp - IRC Chatlog
Search
1:23:09
kakuhen
Most CL implementations signal an error when a TEST and TEST-NOT key is supplied to FIND. I am unable to find where this behavior is documented in the specification (or cleanup issues like TEST-NOT-IF-NOT).
1:23:42
kakuhen
Is there any source for this? Or is this beahvior just a convention that implementations decided to adopt?
1:25:09
specbot
Satisfying a Two-Argument Test: http://www.lispworks.com/reference/HyperSpec/Body/17_ba.htm
8:51:06
beach
I see now that the notification was due yesterday. It may take a day or two more sometimes. There are situations where the program committee has a short debate.
8:52:46
beach
"<selwynning> so it would be nice to know roughly when the invitations will be sent out"
8:53:18
beach
I took that to mean that selwynning had an accepted paper, but did not know whether an invitation to present it was going to be made.
8:55:00
beach
The number of slots for paper presentations is limited. So if there is a large number of submissions, there could be tough decisions about which papers to reject, even if they are fairly good.
8:55:39
beach
Again, the date for author notification was yesterday, but it may take another few days.
8:56:17
beach
There could also be a debate among members of the program committee if there is a strong disagreement between different referees of some paper.
9:07:37
beach
Occasionally, a referee flakes out entirely. And then the program chair must decide whether two referees will be enough on some papers, or whether someone else can replace that person with very short notice.