-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to modify the elements of a tuple in an inline for loop #14705
Comments
verdog
added
the
bug
Observed behavior contradicts documented or intended behavior
label
Feb 22, 2023
mlugg
added a commit
to mlugg/zig
that referenced
this issue
Jun 9, 2023
Resolves: ziglang#13852 Resolves: ziglang#14705
mlugg
added a commit
to mlugg/zig
that referenced
this issue
Jun 14, 2023
Resolves: ziglang#13852 Resolves: ziglang#14705
mlugg
added a commit
to mlugg/zig
that referenced
this issue
Jun 14, 2023
Resolves: ziglang#13852 Resolves: ziglang#14705
wooster0
pushed a commit
to wooster0/zig
that referenced
this issue
Jun 15, 2023
Resolves: ziglang#13852 Resolves: ziglang#14705
wooster0
pushed a commit
to wooster0/zig
that referenced
this issue
Jun 15, 2023
Resolves: ziglang#13852 Resolves: ziglang#14705
wooster0
pushed a commit
to wooster0/zig
that referenced
this issue
Jun 15, 2023
Resolves: ziglang#13852 Resolves: ziglang#14705
Techatrix
added a commit
to zigtools/zls
that referenced
this issue
Nov 17, 2023
- fix data race when allocating with thread safety - remove workarounds for ziglang/zig#14705 - correct unnecessary uses of 'var' Note that the BSD Zero Clause License has been removed from binned_allocator.zig
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Zig Version
0.11.0-dev.1711+dc1f50e50
Steps to Reproduce and Observed Behavior
In zig
0.10.1
(last stable release) this works:But in zig
0.11.0-dev.1711+dc1f50e50
, it seems to be impossible (starting with same source as above):And the new
&
syntax gives me:Expected Behavior
There should be some way to iterate over a tuple and pointer capture its elements.
This is similar to #13852 but I thought it was just unique enough for a new issue.
The text was updated successfully, but these errors were encountered: