Skip to content

[opt] Fix array_untuple bug by properly excluding unhandled node operands#4241

Merged
copybara-service[bot] merged 1 commit into
mainfrom
test_914322574
May 13, 2026
Merged

[opt] Fix array_untuple bug by properly excluding unhandled node operands#4241
copybara-service[bot] merged 1 commit into
mainfrom
test_914322574

Conversation

@copybara-service
Copy link
Copy Markdown

[opt] Fix array_untuple bug by properly excluding unhandled node operands

When an unhandled node (e.g. invoke) returned an array of tuples, the external-group-finding analysis in ArrayUntuplePass incorrectly skipped checking the node's operands due to an early continue. This caused unsupported array-of-tuples arguments passed to that node to remain eligible for untupling, resulting in broken state mutations and incorrect correctness outcomes.

This change removes the early continue, ensuring that operands of all unhandled nodes are correctly identified and excluded from untupling, preserving package semantics.

#geminiassisted

…erands

When an unhandled node (e.g. `invoke`) returned an array of tuples, the external-group-finding analysis in `ArrayUntuplePass` incorrectly skipped checking the node's operands due to an early continue. This caused unsupported array-of-tuples arguments passed to that node to remain eligible for untupling, resulting in broken state mutations and incorrect correctness outcomes.

This change removes the early continue, ensuring that operands of all unhandled nodes are correctly identified and excluded from untupling, preserving package semantics.

#geminiassisted

PiperOrigin-RevId: 914673404
@copybara-service copybara-service Bot merged commit 03eca3d into main May 13, 2026
@copybara-service copybara-service Bot deleted the test_914322574 branch May 13, 2026 06:33
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