refactor(os): migrate callers to CurrentProcess.executable and remove Process.executablePath #304
Loading…
Reference in a new issue
No description provided.
Delete branch "loop/251-current-process-migrate"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #251
Part 2 of #251 (part 1 landed with #262). The published seed
torb-seed-5f22f071d02f(nightly-20261010) hasCurrentProcess, so the compiler can call it.CurrentProcess.executable():project/toolchain.trb(findingstd/andruntime/),cli/run.trb(toolchain key),cli/host.trb(script host key),debugger/adapter.trb, the registry's tests,tests/conformance/print-reaches-a-pipe.trb.Process.executablePathremoved fromstd/process, the natives manifest,runtime/process.c,torb.h, the VM substitute (torb_machine_process_executable_path,thunks.trb,torb_machine.h).torb_natives.handmachine_natives.cupdated (one thunk removed, the ones after it renumbered, count 259 -> 258);compiler/tests/natives.test.trbandbytecode.test.trbcompare them withtorb natives --header.process-executable-pathremoved:current-processmakes the same checks under the VM and--native.standard-library/process.md,os.md,tooling/torb-run.md,design/OS.md(how it landed),design/VM.md,RELEASE.mdfact 5,runtime/README.md, and the mirrored skill references.No local build (heavy builds run in CI only); the forge CI runs the gates.
a3d5dd326b11be684666CurrentProcessidentity, executable and working directory (OS slice 2, part 2) #251Review of
11be684(round 1). CI is green for this head (bootstrap, tier A/B, registry tests, pdisc, natives/bytecode comparison withtorb natives --header; the cross-host jobs are skipped by the workflow, not failed).print-reaches-a-pipe;current-processkeeps the VM/native executable checks, so removingprocess-executable-pathloses no coverage.Process.executablePathcallers migrated with equivalentSome/None->Ok/Errhandling; the native, manifest,torb.h, VM substitute, thunk table and generatedtorb_natives.h/machine_natives.care removed consistently (no leftover reference in the head tree besides history in the design docs and the unrelated VS Code settingtorbscript.executablePath).torb_platform_executable_pathstays and is still used byCurrentProcess.Non-blocking:
docs/design/OS.mdand the later sections ofdocs/design/RELEASE.mdstill describeProcess.executablePath()in the present tense in places (history sections, fine as is).