-
Anyone who can save at all is already a GDocs user, and "Save as" has no meaning to them. Let's stick with the GDocs convention instead.
-
The phrase "Show program execution trace" is poorly chosen. We should not use the word "execution". It's an emotionally loaded word with negative connotations.
-
`rotate` canonicalizes its angle by using `jsnums.remainder`, which asserts that its arguments are both integers. This is silly and unnecessary, and limits the programs we can write.
-
This issue is also filed as a consequence of #1369.
#1369 is a bug in the compiler, but to me, the current behavior is not 'intuitive'. In addition, according to #639 and #972, triple quoted string…
-
Attempting to use `spy` with an assignable variable produces a strange error message:
```
var x = 1
spy: x end
```
The docs don't say whether or not `spy` should work with assignables, bu…
-
Let's document synchronous I/O. We can start by documenting how Pyret does synchronous I/O with Stopify and then tweak the API as needed.
-
When Pyret pauses the stack, you can restart it in more than one way.
The important one is that the client of `pauseStack` can choose to call `resume` or `error` callbacks; the latter simulates a `…
-
```
data File:
| file(name :: String, size :: Number, content :: String)
end
fun get-sizes(lof :: List) -> Number:
cases (List) lof:
| empty => 0
| link(f,r) =>
f.size + 1 …
-
While programming in Pyret, I have found that using provide statements was awkward. At the time, it was possibly undocumented and the syntax differed between provide and provide-types.
Furthermore …
-
I'd expect `scale-xy(-1, 1, an-image)` to produce a flipped image. At the REPL, at least, it doesn't display anything at all. @schanzer is this a bounding-box issue, a rendering issue, or just some …