SRFI 125, 126 Arthur A. Gleckler (01 Feb 2016 18:36 UTC)
|
Re: SRFI 125, 126
taylanbayirli@xxxxxx
(01 Feb 2016 22:34 UTC)
|
Re: SRFI 125, 126
John Cowan
(02 Feb 2016 19:54 UTC)
|
Re: SRFI 125, 126
Arthur A. Gleckler
(03 Feb 2016 01:05 UTC)
|
Re: SRFI 125, 126
John Cowan
(07 Feb 2016 04:40 UTC)
|
Re: SRFI 125, 126
Alex Shinn
(04 Feb 2016 05:09 UTC)
|
Re: SRFI 125, 126
John Cowan
(04 Feb 2016 05:58 UTC)
|
SRFI 125, 126 Arthur A. Gleckler 01 Feb 2016 18:36 UTC
Hello, John and Taylan. SRFI 126 just went into final status, and I'm guessing that SRFI 125 be finished sometime soon, too. Since both cover hash table APIs, and indeed since 126 was written specifically as an alternative to 125, it would be useful to compare them. After SRFI 125 goes into final status, would you each be willing to publish a message giving your design rationale with respect to the other SRFI? There's nothing that says that both SRFI can't be provided by the same Scheme implementation, but it would be nice for implementors to hear "from the horse's mouth," so to speak, why each of you made the decisions you did. Thank you both.