Carl Gay

It is exactly having to come up with workarounds like that that I would like to avoid. I **want** to rework the libraries and make life better for newcomers (and...

Notes from @housel: > `` was originally in system, but io contained an implementation of unbuffered I/O used for `*standard-output*` etc, so if you redirected stdout or stderr it was...

I didn't point out that it *says* "Inferred **types** in call" but then goes on to list things that aren't really types. I missed that several of the arguments were...

Also also also, `common-dylan-test-suite` includes `dylan-test-suite`, I assume for similar reasons.

Useful examples. It looks to me like the parser reaches the `fi` token and, it not being `if`, the parser decides that `end` terminates the `if` statement. Then it is...

Note that sometimes the easiest thing may be to use the playground: https://play.opendylan.org/shared/7b5a2926995b709a

This looks like the same issue to me, but with `#rest`: ``` check-condition("rest one key call one arg", , begin local method m (#rest k, #key) k end; // Stifle...

I think they shouldn't contain the entire .lid file, they should just augment it. They could reference it via the existing LID: header. Need to write down exactly what the...

So, either automatically rebuild the library that had serious warnings, or automatically redisplay the warnings upon recompilation even if that library doesn't otherwise need recompilation. Note that [edit: automatically redisplaying...

On the same general topic, but probably a different bug, I notice that if I add the `Executable:` keyword to the LID file the library doesn't get recompiled and the...