Check your file before you submit
Copying code out of a web page and into a file goes wrong in a few predictable ways. The commonest one is losing the use context starter2024 line off the top, and the error you get afterwards does not mention it — Pyret complains that a name like length is unbound instead, which sends you looking in the wrong place.
Drop your .arr file below and this page will tell you which of those things happened.
Your file stays on your computer. It is read in the browser and never sent anywhere, so this works the same whether you are at home or in Sutliff 105.
.arr file here
or click to choose one
What this checks
- The
use context starter2024line — missing, misplaced, or naming a different context. - Curly quotes, en and em dashes, and the single-character ellipsis, which look almost the same as the plain versions and are not accepted.
- Non-breaking spaces and zero-width characters, which are invisible.
- An empty file.
What it does not check
Whether your program is right. It does not run your code, does not look at your tests, and does not know what the assignment asked for. A clean result here means the text made it into the file intact — open it in Pyret to find out anything else.