Ben Lerner

That's annoying -- this is an unfortunate interaction between being annotated with `List` (which `modes` _is_) and the fact that our dynamic annotation checkers don't check element types (because it's...

@jpolitz this paper-cut issue has been on my todo list for a while. I'm not sure what the best fix is. One approach is to change the implementation of `builtins.raw-array-sort-nums`...

We have some other places in libraries where we have crummy output due to lack of runtime type-testing of the contents of lists, e.g. `color-list-to-bitmap([list: 1, 2, 3, 4], 2,...

I think it's _probably_ fair to start the REPL off in the result of evaluating the `use context` line -- but we do have to be careful. For courses that...

This was a change we made to preserve the pinholes of the "first" images in beside & above, because otherwise pinhole information is lost by that composition. If you want...

There is a heuristic I've used in a different implementation of this image library (not in Pyret), where pinholes are preserved only when the images are overlaid on their pinholes...

1) This is a non-sequitur for the `pyret-lang` repo, right? This is a CPO-related question? 2) I don't have any support for pygments at the moment, and I don't see...

I couldn't figure out which context you were asking for this in. :) Pyret syntax highlighting is _slightly_ tricky, in that there are a few places where the highlighting is...

I got back and forth on the table-operations syntax quite a bit. With a bare identifier in the `using ...` position, I can't decide whether I _want_ to read it...

That's not really possible in any plausible engineering sort of way. `reactor` is a token recognized by the lexer, so this will intrinsically produce a syntax error. You'd have to...