Fatal error: Bad machine state #736
Comments
|
Thanks for the report, and glad you're enjoying the game! Just a quick guess, this is probably #681. But I'll take a closer look tomorrow. |
|
After looking into this a bit more, I'm now quite certain this is an instance of #681. The binding of As a workaround, you could try renaming one of the occurrences of But I really need to fix #681, it is a kind of embarrassing bug. 😳 |
|
Successful workaround, thanks! I'll stick to unique local names. |
…tate (#1928) The big idea of this PR is to add a new type of CESK machine state, `Suspended`, which is a state the base robot automatically goes into after completing execution of a program entered at the REPL. It is as if the base robot is still within the local context of any definitions etc. entered previously, just printed out an "intermediate result", and is now waiting to find out what the next term to be executed will be. This allows us to treat `def` as syntax sugar for `let` and results in a much cleaner way to manage the context of definitions, which in turn allows us to remove a whole lot of special cases and fixes several annoying bugs. See #1087 for more explanation and discussion. Things that are **deleted** (!) by this PR: - `TDef` (`def` is now just syntax sugar for `let`) (#997) - `VResult` (we no longer need to return anything other than plain values) - `FUnionEnv`, `FDiscardEnv`, `FLoadEnv` (we no longer need machinery to collect up definitions while evaluating terms) - `ProcessedTerm` (just a plain `TSyntax` (i.e. `Syntax' Polytype`) is now enough) - `Module` (it only existed to package up some contexts with typechecked terms, but we don't need them anymore) - `RobotContext` and `topContext` (we don't need to store those things separately any more, they are just stored in the `CESK` machine where they belong) Additions/changes: - The `Requirement` module is split into `Requirements.Type` and `Requirements.Analysis` to avoid circular module imports - New `Suspended` state for the CESK machine - `def` and `tydef` are now allowed anywhere (even nested inside other definitions etc.) since `def x = y end; z` is just syntax sugar for `let x = y in z` (see #349) - Code size decreased slightly for many programs using `def`, since `def` is now a synonym for `let`, and consecutive `def`s therefore do not require a `bind`. Closes #1087. Fixes #681 (hence also #736, #1796). Fixes #1032. Closes #1047. Closes #997. Fixes #1900. Fixes #1466. Fixes #1424. See also #636.
Describe the bug
See screenshot
To Reproduce
Here's my script file: https://gist.github.com/rybern/4f42f178ae3b987613eabf2290d1b8d3
You can see the last command I ran; I don't know what other context is relevant
Expected behavior
The bot should keep farming :)
It seems to halt at the second iteration of
farm2NextScreenshots
Additional context
By the way I am loving this game!
The text was updated successfully, but these errors were encountered: