Skip to content

Say that termcade_init has to come first #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nicodes merged 1 commit into from
Aug 3, 2026
Merged

Say that termcade_init has to come first #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/abi.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,11 @@ Instantiation runs `_initialize` (package initializers), never `main`.
memory. The HUD pointer is valid until the next guest call; the pixel
buffer pointer must stay valid for the instance's lifetime.
- The host calls exports one at a time from one goroutine; no reentrancy.
- **`termcade_init` comes first.** It is what constructs the game, so every
other export except `termcade_abi` traps until it has run — a guest written
in Go dereferences a nil game and takes the instance down. The arcade calls
`termcade_abi`, then `termcade_init`, then `termcade_playfield`, and any
other host must do the same.
- Per-call budgets: 5s for setup calls, 500ms per frame call. A call that
exceeds its budget kills the instance.

Expand Down