Skip to content

v1 resolve is still superlinear - #6676

Closed
gunbai-bot[bot] wants to merge 9 commits into
mainfrom
session/sleek-ram-450
Closed

gunbai-bot[bot] wants to merge 9 commits into
mainfrom
session/sleek-ram-450

Conversation

@gunbai-bot

@gunbai-bot gunbai-bot Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Auto-opened by session-dashboard for session sleek-ram-450.
Pushing to session/sleek-ram-450 advances this PR.

Worker attestation

Before flipping this PR to ready for review, confirm each item:

  • Title describes the change (not the session id or branch).
  • PR body summarises what and why (replace the TODO below).
  • Tests run: name the command (e.g. npm test, cargo test) and the result.
  • If this closes a work item, the body contains a Closes #N directive.
  • No commits on this branch are surprises (no fork/cherry-pick I did not make).
  • No secrets / credentials / large binaries staged.

Summary

TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.

Test plan

  • TODO: list the commands that ran (or "no tests changed; relied on CI") and the outcome.

briansrls and others added 9 commits July 15, 2026 03:50
…pute to Rc-borrow

build_type_env / build_type_env_unresolved recomputed ancestry_str_bindings as a
fresh per-module map_merge(parent.interface.env.ancestry, parent.interface.env.str)
in the single-import case. That value is byte-identical to ancestry_cache.str_bindings
(already Rc-shared): interface.cache.str_bindings == map_merge(env.ancestry, env.str)
by construction, and for count==1 the union of one parent cache IS that cache,
Rc-shared unchanged. All three branches resolved to ancestry_cache.str_bindings, so
the conditional collapses to one Rc-borrow -- killing the per-module fresh-HAMT
allocation and the O(M^2) map_merge/SipHash churn on single-import chains (the
04_env.dag line-79 dissolution trigger). Regenerated seed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The auto-committer's stale merge of an OLD origin/main left the committed
stage0 seed inconsistent with the merged .dag authority, reding
generated_artifact_drift_gate on CI. Merged current origin/main and
regenerated stage0 from the merged tree; only cli_run.rs changed (main's
committed copy was itself drifted from a fresh regen). regen --verify:
regen_divergence_count=0. The ancestry_str_bindings collapse is unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@gunbai-bot

gunbai-bot Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor Author

Closing as net-empty. This draft's only code deliverable — the single-import ancestry_str_bindings Rc-borrow collapse — already merged to main via #6660 (squash 56d8f155d8). The remaining commits on this branch are main-merges plus a throwaway per-item typecheck probe (GUNBC_ITEM_PROBE) that I reverted, so git diff main...HEAD is empty.

The follow-on work (profiling the multi-import resolve exponent per the #6663 implementer notes) produced a measurement report, not code — reported to the operator, awaiting direction on which lever to pursue. A real code deliverable will get a fresh PR. — sent from sleek-ram-450

@gunbai-bot gunbai-bot Bot closed this Jul 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant