Skip to content

Conversation

@mlugg
Copy link
Member

@mlugg mlugg commented Jun 9, 2023

I promise I'm not trying to make a habit of implementing non-accepted proposals: I wrote this code as a fix for #14705, then while skimming the issue tracker for related bugs found that this implements #13852. In all honestly, I thought this was already an intended behavior, and I think that proposal should be fairly uncontroversial.

Resolves: #13852
Resolves: #14705

@mlugg mlugg force-pushed the fix/for-tuple-byref branch from 2753eba to 8d305d2 Compare June 14, 2023 12:41
@mlugg mlugg force-pushed the fix/for-tuple-byref branch from 8d305d2 to a615638 Compare June 14, 2023 13:51
@andrewrk andrewrk enabled auto-merge (rebase) June 14, 2023 18:31
@andrewrk andrewrk merged commit ce88c43 into ziglang:master Jun 15, 2023
@mlugg mlugg deleted the fix/for-tuple-byref branch May 18, 2025 20:08
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.

Unable to modify the elements of a tuple in an inline for loop Pointer to tuple does not auto-dereference when accessed as indexable

2 participants