Skip to content

stored_projection: a field that is also assigned is not decided by its literals - #7

Merged
alii merged 2 commits into
masterfrom
assigned-fields-are-not-projections
Aug 14, 2026
Merged

stored_projection: a field that is also assigned is not decided by its literals#7
alii merged 2 commits into
masterfrom
assigned-fields-are-not-projections

Conversation

@alii

@alii alii commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Closes #6, the ParseTask half. There the Option field the lint paired with the enum is filled in after construction (task.ctx = Some(..) in two places), so the literals were never the whole story.

Any x.f = .. on a local struct now takes f out of the pairing for that struct. On bun this drops the ParseTask finding and keeps the other two.

The GetActiveCfg half of #6 is the lint working as described, just on a 2 site type, so nothing here for that.

@alii
alii merged commit 4e08693 into master Aug 14, 2026
2 checks passed
alii added a commit to oven-sh/bun that referenced this pull request Aug 14, 2026
Picks up scarletindustries/mordant#7 (a field that is also assigned is
not a stored projection), which removes the ParseTask entry from the
baseline.

Regenerating the baseline also added one entry that has nothing to do
with the bump: asymmetric_guard on the free_resources call #38044 added
in h2_frame_parser.rs. Looked at it; freeing the stream on the
transition to CLOSED is right whatever can_send_data reads, so it is
baselined rather than changed. First time that lint has fired here, so
keeping an eye on whether it earns its place.

bun run rust:mordant is clean with the new pin and baseline.
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.

stored_projection: two low-site findings on bun at fc46d7f

1 participant