Finish Star-Lang Common Lisp implementation hardening #47
Labels
No labels
bug
design
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
research
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/starintel-auto-research#47
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
PR #43 approves Common Lisp as the sole Star-Lang implementation language and freezes the architecture direction. This issue tracks implementation work that remains incomplete and must not be represented as finished by the decision PR.
Work
lost-rob0t/star-langPR #11.lost-rob0t/star-langPR #11 source-preserving compiler foundation.lost-rob0t/star-langPR #19; current shellcurl/sha256sumimplementations are now compatibility adapters behind injected resolver effects. Native Common Lisp adapters and shell removal remain Phase 2. Research/design: Auto Research PR #110 (STAR-LANG-RESEARCH-016,STAR-LANG-005).lost-rob0t/star-langPR #3;asdf:test-system :starlang-prototypeis the transitional authoritative entry point.lost-rob0t/star-langPR #16 with byte comparisons and SHA-256 verification green in CI/Nix.Additional conformance landed since this issue was opened
lost-rob0t/star-langPR #14: canonicalstar://domain:address:actor-nameservice identity, runtime-directory discovery, and deterministic/runtime dispatch integration from approvedSTAR-LANG-004.lost-rob0t/star-langPR #15: exactsha256:<64 hex digits>lock validation across retained compiler/spec-domain compatibility paths, with CI and Nix green.lost-rob0t/star-langPR #16: frozen FEC/BBP canonical manifest bytes and SHA-256 compatibility gates, with CI and Nix green.lost-rob0t/star-langPR #19: injected resolver digest/fetch effect protocol, fake-port regression coverage, and transitional shell adapters, with CI and Nix green.Completion gate
The implementation tracker may move from
IMPLEMENTINGtoAPPROVEDonly when the acceptance ledger is complete and the Star-Lang Common Lisp workflow validates the final package layout.