agent: builder model: opus max_turns: 80 budget_usd: 16 —

Brief: #1065, a call through a struct field holding code passes its arguments unlent

Score: compiler bug, a wrong lowering that reaches rustc (a list unborrowed, an owned text moved) where Part I and ADR-282 D2 say the compiler lends; found by b12, small and traced.

Facts: Where things live, Traps already met, Commands

Issue #1065 (summary)

A call through a field holding code (h.f(x)) does not lend its arguments; the same call through a let or a parameter (g(x), apply(count, x)) does. Not about pausing: sync or not, one view or two.

Probe (checked on 46e6179f’s binary, each fails in rustc):

struct H { f: fn(ref Vec[i64]) -> i64 }
fn count(a: ref Vec[i64]) -> i64 { a.len() }
fn main() {
    let h = H { f: count }
    let x = [1, 2, 3]
    println(h.f(x))          // rustc: Mismatched types, expected `&[i64]`, found `Vec<{integer}>`
}

Suspected location (traced by reading, fairly sure)

To build

  1. Reproduce rows a-c on the unfixed binary; keep the result under Tests:.
  2. The checker and emitter fix above, with their lowered twins (lower-std, fixpoint).
  3. Test tests/compiler/tests/a_field_call_lends.nika + .stdout holding rows a-c, failing on the unfixed binary. Commit check, emit: a call through a field holding code lends its arguments (Fixes #1065).

Done when

The new test fails on the unfixed compiler and passes through nikaia test --project tests/compiler --both-settings, with the tests whose names contain field, kept, code_param, function_type, lambda (by name); lower-std fixpoint clean; build, fmt, clippy, pre-push-check.sh; committed locally. Changelog: one line.

Stop and report if

An edit is needed outside check_core_args.nika, check_core_call.nika, emit_core_reads.nika, emit_core_args.nika, their lowered twins and the new test; an error in another agent’s file.

Not yours, never stage: every file git status shows modified or untracked at your start (lowered/project_members.rs is uncommitted residue), and every docs/briefs/* file except your report.

Rules (CLAUDE.md; this block is pasted into every brief, also a fix-forward)

Report (at most 15 lines, to exactly /home/user/Nikaia/docs/briefs/bugs/b16-1065-field-call-lends.md.report.md)

Fields of docs/architect.md, Briefs and reports: Result: done|noop|partial|blocked (the bare word alone on that line: Result: done, never a summary after it, which cuts the batch, b869a 2026-10-27; Owner: is a question for the owner or none, never a role), Files, Commit, Body (optional, one paragraph for the commit message), Fixes, Pushed, Tests, Gate (green|red), Deviation, Found, Needs, Changelog, Owner, Disk freed, and for a move Rs2nika: (the kept N of M lines of rs2nika --score, then the three costliest hand edits; none for a task that moves no Rust, none (redesign) for a brief with Shape: redesign and no Convert: line). none where nothing, and then the bare word: Deviation: none (a note) cuts the batch (batch.nika compares exactly); a note goes into the commit message. Found: is only for a defect outside your change (it cuts the batch); a process event such as another session resetting or rewriting your files is no Found:, it goes under Needs: (m3a 2026-10-28); a converter draft that came out wrong is no Found:, it is one of the costliest edits under Rs2nika:, which the converter lane reads (e12-4b 2026-10-27); how you solved your own step goes into the commit message. Deviation: is only a step of the brief built otherwise than written or not built (a choice the brief left to you, such as keep what X needs and say so, is no deviation: it goes into the commit message; nor is building two steps in one commit when every step is built, e12-3a 2026-10-27, nor a step another commit on develop already built, shown by your test failing with that commit’s change reverted, b889 2026-10-27: name the commit in Body:, nor a test’s expected .stdout/.stderr taken from what the program really prints where the brief’s sketch of it was short or wrong, b934 2026-10-29: say so in Body:, nor a lowering that follows the ADR governing it where the brief’s expected lowering contradicts that ADR, b933 2026-10-29: name the ADR in Body:, nor a lowering other than the brief’s where rustc cannot take the brief’s, b1029 2026-10-31: say why in Body:, nor re-keying an allow-list entry (KNOWN) whose hash changed for the same program and the same reason, b-fixforward-sweep2 2026-10-28: say so in Body:, nor an existing test’s expected .stdout/.stderr updated because your change rightly changes the message it prints, b1012b 2026-10-31: name the test in Body:); how you verified (e.g. a test not run against the unfixed compiler) goes under Tests:. A noop says why under Tests: (what was probed), not under Deviation:. Final answer, one line: done <sha>, report <path> (or BLOCKED: ... / PUSH REJECTED ...).

Attribution: Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com Claude-Session: https://claude.ai/code/session_01GFeMqxRbtUMiGVyDMxsvEq

This site is open source. Improve this page.