Joe Politz

Radical proposal: Pick a cutoff after which exact rationals turn into roughnums, determined by (for rationals) the size of the numerator and denominator, and (for bignums) after a certain large...

+1 to Ben's comment relative to this issue. This issue would be a problem if the numbers library were 10x or 100x faster. That said, it's not a _bad_ idea...

Can you paste the errors?

The second makes sense and is quite easily fixable; there's a template file that we copy into standalone JS files that is located relative to the working directory. The first...

Thanks for asking. This has been a longstanding issue where we aren't sure what we want. For example: https://github.com/brownplt/pyret-lang/issues/307 https://groups.google.com/g/pyret-discuss/c/FUb96Hnobuw/m/iH_Vh6UIDFgJ The weird output in that issue is just a symptom...

To _further_ narrow this down, this only happens on types that are written as `SomeName%(predicate)`, then provided, then `include`d. For a record type, for instance, like `{x :: Number}%(x-is-integer)`, this...

And they probably should be called fold-left and fold-right, to avoid unnecessarily making things sound cryptic. That goes for the method names, too. It might be better to call them...

Nice, I like that. Is there any better word than `fold` to use here? That's the last remaining piece of jargon in the name.

After lecturing on fold today, I realized that `fold-backward` might be kinda confusing, since (assuming we mean fold-right by fold-backward) it is the one that keeps the list in order...

I like this idea. Vocab question – is "docstring" the word we should use to refer to triple-quoted strings? What about "string blocks" or "multi-line strings"? On Tue, Aug 22,...