Ross Angle

Anyhow, that's petty of me, it brings in the unrelated topic of `map` -- please nobody dig into that here, I don't wanna derail -- and it isn't even really...

The difference between operations like these is like: ```racket (call/cc (lambda (k) ...)) (let/cc k ...) ``` The primary distinguishing factor here is the nesting level, which causes one to...

I sympathize with this issue. I think it could be approached like this: - In an argument list, allow some kind of syntax that binds an optional argument to an...

@Metaxal I'm really glad you arrived somewhere you like. Incidentally, I don't think it's just a slight variation on what I proposed; I was basically saying "here's how we can...

That's right, and I don't want to give the wrong impression that it's a simple proposal. I think it's similar in scope to keyword arguments. There would be a new...

Thanks for hearing my concerns. Those are thoughtful answers. The workaround I would probably use is an immutable box. You don't find uses for an immutable box every day. 😛...

Looks wonderful to me! I think I'm fresh out of other suggestions. :)

I think giving compound structure to declarations at the top level of a file has a lot in common with parsing. Instead of a sequence of tokens, it's a sequence...

Looks to me like that's exactly what's needed for `define*`. :) I think a lot of the rest of what I described above could be implemented as a library in...

On the other hand, an annotation probably wouldn't make a great example either. I think there's quite a bit of subtlety to take into account when trying to consume a...