Skip to content

merge queue: checking #2500 on master (7e09e8e) - #2517

Closed
mergify[bot] wants to merge 2 commits into
masterfrom
mergify/merge-queue/de5050e148
Closed

mergify[bot] wants to merge 2 commits into
masterfrom
mergify/merge-queue/de5050e148

Conversation

@mergify

@mergify mergify Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Note

This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch primitive-brie-f3zu5a of the changes queue, to test #2500 before it merges into master. Pushing to this branch or closing this pull request removes #2500 from the queue.

What this draft tests

Mergify checks that #2500 still passes CI on top of master. CI runs on this draft's code, built in this order:

  1. master at 7e09e8e
  2. #2500, the pull request of this batch

🎉 Where it stands: checks passed

CI passed on this draft.

Follow the changes queue in the dashboard

What happens next

  • Mergify merges #2500 into master and closes this draft.
Metadata for CI tooling, read by mergify ci
---
all_scopes: false
checking_base_sha: 7e09e8e71969276012d9e47ee62f37ae16b69d78
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 2500
    scopes:
      - core
scopes:
  - core
...
1 scope
  • core
Required conditions of queue rule changes for merge
  • check-success = Conventional Commit title
  • check-success = Queue validation
  • any of [🛡 GitHub repository ruleset rule master]:
    • check-success = @github-actions/Lint & Format
    • check-neutral = @github-actions/Lint & Format
    • check-skipped = @github-actions/Lint & Format
  • any of [🛡 GitHub repository ruleset rule master]:
    • check-success = @github-actions/Rust Test & NAPI Build
    • check-neutral = @github-actions/Rust Test & NAPI Build
    • check-skipped = @github-actions/Rust Test & NAPI Build
  • any of [🛡 GitHub repository ruleset rule master]:
    • check-success = @github-actions/JS Test (Ubuntu)
    • check-neutral = @github-actions/JS Test (Ubuntu)
    • check-skipped = @github-actions/JS Test (Ubuntu)
  • any of [🛡 GitHub repository ruleset rule master]:
    • check-success = @github-actions/Conventional Commit title
    • check-neutral = @github-actions/Conventional Commit title
    • check-skipped = @github-actions/Conventional Commit title
  • any of [🛡 GitHub repository ruleset rule master]:
    • check-success = @github-actions/Queue validation
    • check-neutral = @github-actions/Queue validation
    • check-skipped = @github-actions/Queue validation
Required conditions to stay in the queue

tignear and others added 2 commits October 29, 2026 13:27
… reads

Review findings on the unpacked structure stack (#2415, #2422, #2424)
that arrived after it merged:

- A `default` pattern item descends into a structure member unless the
  value is a structure of that member's type (IEEE 1800-2023 10.9.2), so
  `c = '{default: a}` initializes the nested members of `a`'s type
  instead of rejecting it.
- 4-state object fields store their complemented value and mask planes
  masked to the field width. Padding bits stay zero, so a default record
  of a field that is not byte-aligned (`logic flag`) is all zero bytes,
  and `finish_record` keeps it `null`: `d = new[1]; d[0] = d[0];` no
  longer wakes `@(d)`.
- `q.pop_front` and `q.pop_back` without parentheses are whole elements
  of a queue of structures.
- A `$` index of a queue read through a receiver with a side effect, such
  as `m[f()][$]`, is rejected: the size behind `$` reads the receiver
  again, which could name another queue.

Change-Id: Ibd97e9c73adb7703a0734ca9fcdedeb66c0a2189
@mergify mergify Bot closed this Oct 29, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/de5050e148 branch October 29, 2026 05:11
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