tape check
Usage
bash
tape check <file.tape>Purpose
Runs the frontend pipeline through type checking without generating code. Useful for fast feedback in editors and CI.
bash
tape check app.tape
# OK
tape check broken.tape
# broken.tape:12:5: error: type mismatch: expected i64, got stringWhat it does
- Split source into regions
- Parse
#coderegion (no rt0 preamble — single-module only) - Parse
#viewregion, merge components - Execute
@tapeblocks (compile-time metaprogramming) - Type check
Prints OK on success. Errors go to stderr.
Options
| Flag | Description |
|---|---|
--human | Human-readable errors with color and source context |
--max-errors <N> | Stop after N errors |
-I <path> | Add module search path |
Exit codes
| Code | Meaning |
|---|---|
| 0 | No errors |
| 1 | Parse errors, comptime errors, or type errors found |
Speed
tape check skips:
- TAC lowering
- Link checking
- Native codegen
- Binary emission
It’s the recommended command for editor integrations and pre-commit hooks.
Last modified: