Ben Lerner

Yes. @jswrenn is implementing something like this, separate from Pyret itself, and we ought to incorporate some of that work back into Pyret.

Can you give a concrete message you'd like to see? My initial attempts at wording such a message choked on my _own_ "too many words!" threshold, so they certainly wouldn't...

That's a non-trivial design problem too. Pyret documentation links aren't stable (especially if we're revising the organization of the docs every so often); there's no representation of links in the...

I would like our errors to be nicer, and to have a good way of linking to docs. I can't spend too much time thinking about this today, but some...

I had commented (https://github.com/brownplt/pyret-lang/commit/b5dfaa321d443c40e409c1ccdd9ae9b3cc1a9dbd#r41383423) about this and committed (https://github.com/brownplt/pyret-lang/commit/92ec0c056e31b34adea64b86aa3172fea86f9f3e) a fix, and this PR seems to take a different approach. (In any case, #1525 is effectively currently fixed on horizon,...

If we do go with this PR, then you'll need to revert that commit, or else you won't get back your constructor printing, anyway...

This is odd, and slightly amusing as a root cause. It's not a Cyrillic issue per se; it's any non-Ascii string. It boils down to the checker library calling `string-contains(to-repr(the...

`then` is not a keyword, but `then:` is a color-keyword. So `{then : 5}` would be a valid object, but `{then: 5}` is a parse error. In general, we have...

We've taken pains to avoid doing that precise thing. The idea was to steal as few words from the language as possible. (table, block, examples, doc, otherwise, source, where, with,...

"In this extremely natural scenario"...that only you have encountered, once, in several years of programming in Pyret :) We've now seen a couple of examples (once each) of colon-keywords being...