Hi David,
Sorry for the slow response, but I'd just like to confirm what it seems
you've already intuited about CHICKEN's type system.
Simply put, CHICKEN's type-directed compilation pass will only optimise
a program when it's *certain* that a given type is correct, and it will
only issue a
On Sun, Dec 03, 2017 at 06:46:14AM -0500, David Goffredo wrote:
> So my question is why the compiler doesn't warn on:
>
> (printed foo)
>
> when it can be determined statically that the argument has (rather -- is
> declared to have) an incompatible type. Maybe the types will be compatible
>
On Sat, Dec 02, 2017 at 08:56:52PM -0500, David Goffredo wrote:
> Hello everyone,
>
> I've been playing around with Chicken for about a month now, and so far
> really enjoy it. Even got it building and (mostly) working on crusty old AIX
> and Solaris machines.
Hi David,
Cool! That's very good
Hello everyone,
I've been playing around with Chicken for about a month now, and so far
really enjoy it. Even got it building and (mostly) working on crusty old
AIX and Solaris machines.
I'm new to Scheme in general. My current project will involve some
record types, and I'd like to use
