Cut BACKLOG.md down to what is still open - #1285
Merged
Merged
Conversation
The file was the working memory of a finished loop: it described itself as notes on type class bounds, kept stable item numbers for a LOOP.md that no longer exists, and carried 155 lines of narrative on work whose history is in the commits. Of its Todo items, 10, 13, 23 and 26 are done in the code (`ProgramState` compares type variables through the recorded specialisation, `subclassOfBoundedGenericLua` is a positive test, the erasure model shipped), 9 and 12 were standing practices, and 8 was already marked settled. What stays is what cannot be read off the code: the library's own tests still execute on the interpreter only, the dead overload slot in a specialised class, the fuzz suite's shared output filename, the family instance design question, and the notes that are rules rather than history. The Lua performance items are referenced where they live.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
1 participant
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.
What
BACKLOG.md was the working memory of a finished loop: it described itself as notes on type class bounds, kept stable item numbers for a gitignored
LOOP.mdthat targeted the already-merged #1253, and carried 155 lines of narrative on work whose history is in the commits and PRs. 397 lines become 68.What was verified as done and removed
ProgramState.getCurrentTypeArgumentcompares throughspecialisations.canonical(...)TypeClassTests.subclassOfBoundedGenericLuais a positive testdiv/modresult type@Testis the interpreter unit test by design; the shim-boundedtestLua(true)path is what the suite has, and real-map Lua correctness is asserted in the agent workflow. Recorded as a Note.What stays
Open: the dead overload slot in a specialised class; the fuzz suite writing one fixed output filename for every generated program (torn once in a full run on 2026-09-03, passes alone); a pointer to
LUA_HOT_PATH_SPEC.mdfor the Lua backend performance tasks. Blocked: thecastTo intfamily-instance design question. Notes: the rules that are not history.Order
LUA_HOT_PATH_SPEC.mdlands with #1284. Merge that first so the reference here resolves.