Skip to content

Fix two comments naming builtins that were removed or have since landed - #14

Merged
janstrakowski merged 1 commit into
mainfrom
fix-stale-serialize-comments
Aug 28, 2026
Merged

Fix two comments naming builtins that were removed or have since landed#14
janstrakowski merged 1 commit into
mainfrom
fix-stale-serialize-comments

Conversation

@janstrakowski

Copy link
Copy Markdown
Owner

Two comments in src/ still describe the language as it was before #8.

src/parser.odinpush_wrapped's doc line lists the keyword-prefix
shapes it builds, and still includes serialize/serialize_file, which #8
removed from the language.

src/eval.odin — the file header's list of what this evaluator pass
deliberately leaves unimplemented. Besides the same two removed keywords, it
named three things that run today:

named as unimplemented reality
async implemented — spawn_async, and LANGUAGE.md documents it
sha256 implemented in #8 (eval_sha256, src/hash.odin)
File implemented — File_Value, loadfile, file display

What is genuinely still scoped out is cached, import, #context, and the
static-vs-runtime distinction for check/static_check (one case runs both
as runtime checks). That is what the header now says.

Bytes comes off the list as well: the value type exists and flows through the
evaluator, and the one real gap — no literal syntax for it — is already
recorded at the top of src/value.odin, which is the better place for it.

A header comment enumerating the unfinished work is exactly where someone looks
to find unfinished work, so it is worth keeping true; this one was pointing at
three finished features and two deleted ones.

Comments only — no behaviour change. odin test src is green at 160 tests.

🤖 Generated with Claude Code

`serialize`/`serialize_file` left the language in #8, but two comments still
describe them as live keyword-prefix builtins: `push_wrapped`'s list of the
shapes it builds, and the evaluator's header.

The evaluator header had drifted further than that. Its list of what this pass
deliberately leaves unimplemented also still named `async`, `sha256` and
`File`, all three of which run today - `sha256` since #8 gave it a real
implementation, and `async`/`File` well before that. What is actually scoped
out is `cached`, `import`, `#context`, and the static-vs-runtime distinction
for `check`/`static_check`. `Bytes` comes off the list too: the value type
exists and flows through the evaluator, and the gap that remains - no literal
syntax for it - is already recorded where it belongs, at the top of value.odin.

A comment that lists the unfinished work is worth keeping accurate precisely
because it is where someone looks to find unfinished work; one that names
three finished things and two deleted ones sends them the wrong way.

Comments only, no behaviour change. Suite green at 160 tests.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@janstrakowski
janstrakowski merged commit 31ce353 into main Aug 28, 2026
5 checks passed
@janstrakowski
janstrakowski deleted the fix-stale-serialize-comments branch August 28, 2026 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant