On Tue, Sep 09, 2014 at 02:57:17AM -0700, Evan Hanson wrote:
Hi hackers,
Here are some list-related scrutiny improvements. I started with pair
walking for the scrutinizer's special cases to fix #759 (patch #2),
which made adding special cases for drop tail easy (#3). The other
special
Hi Peter, thanks for all the pushes!
On 2014-10-19 14:34, Peter Bex wrote:
I've pushed these patches, but I had to make one small modification:
the special case for split-at was incorrect.
Thanks for catching that. Indeed, values should be spliced *out* of
their lists. Not sure what I was
Am 09.09.2014 um 15:34 schrieb Moritz Heidkamp:
John Cowan co...@mercury.ccil.org writes:
Thanks, that's helpful. The trouble is that such a file is an internal
(not publicly documented, unstable) format. So if I want to ship portable
code along with type information for Chicken, I have to:
Hi hackers,
Here are some list-related scrutiny improvements. I started with pair
walking for the scrutinizer's special cases to fix #759 (patch #2),
which made adding special cases for drop tail easy (#3). The other
special cases (#4, #5) are basically just improving result type accuracy
for
From: Evan Hanson ev...@foldling.org
Subject: [Chicken-hackers] [PATCH 0/5] List scrutiny special cases
Date: Tue, 9 Sep 2014 02:57:17 -0700
Hi hackers,
Here are some list-related scrutiny improvements. I started with pair
walking for the scrutinizer's special cases to fix #759 (patch #2
Felix Winkelmann scripsit:
Wow, cool. I have to try these patches out. But note that hardcoding
special cases for SRFI-1 procedures is moot, since these will be
thrown of the core system, sooner or later (or in other words: there
will be only internally used variants, possibly with less error
Hi John,
On Tue, 9 Sep 2014 08:03:29 -0400 John Cowan co...@mercury.ccil.org wrote:
Felix Winkelmann scripsit:
Wow, cool. I have to try these patches out. But note that hardcoding
special cases for SRFI-1 procedures is moot, since these will be
thrown of the core system, sooner or later (or
Mario Domenech Goulart scripsit:
If I understand correctly your comment, that's already supported
(http://wiki.call-cc.org/man/4/Types#using-type-information-in-extensions).
Thanks, that's helpful. The trouble is that such a file is an internal
(not publicly documented, unstable) format. So
John Cowan co...@mercury.ccil.org writes:
Thanks, that's helpful. The trouble is that such a file is an internal
(not publicly documented, unstable) format. So if I want to ship portable
code along with type information for Chicken, I have to:
1) insert the type declarations in the code
Felix Winkelmann scripsit:
Wow, cool. I have to try these patches out. But note that hardcoding
special cases for SRFI-1 procedures is moot, since these will be
thrown of the core system, sooner or later (or in other words: there
will be only internally used variants, possibly with less
10 matches
Mail list logo
