source-academy / py-slang / 28800629579

81%

Build Type

push

github

Committed by web-flow

Commit Message

Add a native Pynter/PVML pathway to the standalone repl (#216)

* Add a native Sinter/SVML pathway to the standalone repl

Extends `yarn repl` with `--engine svml`, which compiles a SICPy program to
SVML bytecode and runs it on a native Sinter `runner` binary (built
separately from the sinter repo) instead of the CSE machine. Restricted to
`-v 3`, matching what the SVML compiler currently supports.

Also adds an opt-in parity harness (generateNativeSinterTestCases, gated on
SINTER_RUNNER_PATH) that reruns the existing CSE test suite's TestCases
tables against svml/sinter, to track coverage as the compiler and Sinter
itself gain features.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* Target the native Pyinter fork instead of Sinter for the SVML repl pathway

Sinter is the fallback engine for the live Source curriculum on real
hardware, so it isn't safe to grow Python-specific VM semantics into it.
source-academy/pyinter is a new fork of Sinter, kept as a separate sister
project for that purpose. Repoints the --engine svml CLI pathway added in
the previous commit at Pyinter instead: --sinter -> --pyinter,
SINTER_RUNNER_PATH -> PYINTER_RUNNER_PATH, generateNativeSinterTestCases ->
generateNativePyinterTestCases, and moves the native runner wrapper out of
engines/svml/sinter/ (which still holds the pre-existing WASM Sinter
integration used by PySvmlSinterEvaluator, untouched here) into its own
engines/svml/pyinter/.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* Rename the Sinter fork from Pyinter to Pynter

The sister project's name is Pynter, not Pyinter.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* Fork the SVML wiki docs into docs/pvml/ as PVML's starting point

Copied from the js-slang wiki (SVML-Specification, SVML-Instruction-Set,
SVML-Compiler-and-Machine) so py-slang can start documenting and evolving
PVML — the bytecode format Pynter (the Sinter fork) will run — without
touching the canonical SVML docs.
... (continued)

Coverage Stats

2469 of 3473 branches covered (71.09%)

Branch coverage included in aggregate %.

166 of 230 new or added lines in 10 files covered. (72.17%)

6 existing lines in 1 file now uncovered.

5965 of 7418 relevant lines covered (80.41%)

13502.87 hits per line