Repository navigation
docs: one-command reproduction, and what orchestrate check guarantees - #13
Closed
Immanuel-Fowler wants to merge 2 commits into
Closed
Immanuel-Fowler wants to merge 2 commits into
Immanuel-Fowler wants to merge 2 commits into
Conversation
benchmarks/run_all.py builds the release compiler and runs the boundary ladder, the tick cost and the diagnostics coverage in order, writing every table under benchmarks/results and joining the reports into results.md; the benchmarks README documents it and gains the coverage section. The language reference states in one paragraph what a check does and finds and what it does not, written to be quoted, so accurate rather than flattering. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
All three tables in the README now come from a single end-to-end run of benchmarks/run_all.py, so their headers share one commit, one timestamp and one machine. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #12 (
test/diagnostics-corpus); merge that first. Last of the series.What
python3 benchmarks/run_all.pybuilds the release compiler and runs the boundary ladder, the tick cost, and the diagnostics coverage scripts in order, writing every CSV, JSON, and Markdown table underbenchmarks/results/and joining the three reports intoresults.md.--no-typescript,--skip <step>,--out DIR, andORCHESTRATE=<path>are the knobs. Documented inbenchmarks/README.md, which also gains the diagnostics-coverage section.orchestrate checkguarantees, in one place. A paragraph indocs/language-reference.md(Chapter 5, before "Debugging Generated Code") states precisely whatcheckdoes — parse, resolve modules, register every sidecar including a.wasmmodule's export table, typecheck the entry file — and what it does not: no codegen, no Cargo, library-only rules not enforced, module serverlet bodies not walked, foreign sources not checked. It is written to be quoted, so it is accurate rather than flattering.LIMITATIONS-notes.mdis complete for the series.The series
feat/sandbox-arrays-structsfeat/sandbox-crash-and-grantsgrant callas linker imports;on_crashon the hostfeat/boundary-ladder-benchmarkfeat/tick-cost-benchmarkshared letcodegen fixestest/determinism-tracetest/diagnostics-corpuscheck; sixteen typechecker fixesdocs/check-guarantees-and-reproductionChangelog entry under
[Unreleased]. If a release is wanted, v0.15.0 fits: new features, nothing that worked changed behaviour. Not cut here.🤖 Generated with Claude Code