[Issue 8621] Iteration variable in foreach not closed upon properly in delegate, resulting in completely corrupt large values appearing

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=8621

Iain Buclaw  changed:

   What|Removed |Added

   Priority|P2  |P3

--

[Issue 8621] Iteration variable in foreach not closed upon properly in delegate, resulting in completely corrupt large values appearing

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=8621

Edwin van Leeuwen  changed:

   What|Removed |Added

 CC||ed...@tkwsping.nl

--

[Issue 8621] Iteration variable in foreach not closed upon properly in delegate, resulting in completely corrupt large values appearing

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=8621

ent...@cantab.net changed:

   What|Removed |Added

Summary|Iteration variable in   |Iteration variable in
   |foreach not closed upon |foreach not closed upon
   |properly in delegate|properly in delegate,
   ||resulting in completely
   ||corrupt large values
   ||appearing

--

[Issue 8621] Iteration variable in foreach not closed upon properly in delegate, resulting in completely corrupt large values appearing

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=8621

Gabor Mezo gabor.m...@outlook.com changed:

   What|Removed |Added

 CC||gabor.m...@outlook.com

--- Comment #5 from Gabor Mezo gabor.m...@outlook.com ---
I can confirm that this issue is NOT present on DMD 2.066.0 Windows.

--

[Issue 8621] Iteration variable in foreach not closed upon properly in delegate, resulting in completely corrupt large values appearing

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=8621

--- Comment #6 from ent...@cantab.net ---
Great - I haven't retested recently. Feel free to resolve :)

--

[Issue 8621] Iteration variable in foreach not closed upon properly in delegate, resulting in completely corrupt large values appearing

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=8621

--- Comment #7 from Gabor Mezo gabor.m...@outlook.com ---
We have Still happens on git HEAD (v2.067-devel-cfe52d3) comment above. Maybe
it only appears on Linux, or reappeared in v2.067. Worth a check before goes
resolved.

--

[Issue 8621] Iteration variable in foreach not closed upon properly in delegate, resulting in completely corrupt large values appearing

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=8621

--- Comment #8 from ent...@cantab.net ---
True, I forgot that was there. For what it's worth, I originally encountered
the bug on Windows.

--

[Issue 8621] Iteration variable in foreach not closed upon properly in delegate, resulting in completely corrupt large values appearing

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=8621

Ketmar Dark ket...@ketmar.no-ip.org changed:

   What|Removed |Added

 CC||ket...@ketmar.no-ip.org

--- Comment #9 from Ketmar Dark ket...@ketmar.no-ip.org ---
just checked with HEAD-1d1998 on 32-bit GNU/Linux. first sample prints alot of
'9', second sample prints alot of '0'. so it works at least for 32-bits. maybe
this is 64-bit issue?

--

[Issue 8621] Iteration variable in foreach not closed upon properly in delegate, resulting in completely corrupt large values appearing

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=8621

--- Comment #10 from ent...@cantab.net ---
I think I was working in 32-bit though.

hsteoh, can you tell us more about the situation you reproduced it in?

--

[Issue 8621] Iteration variable in foreach not closed upon properly in delegate, resulting in completely corrupt large values appearing

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=8621

--- Comment #11 from hst...@quickfur.ath.cx ---
Just retested it on Linux/64 (git HEAD), seems that garbage values are no
longer happening. It still shows improper/missing closure over i, though,
because the output is all 9's, meaning that it's closing on a single variable i
shared across all iterations, as opposed to unique values per iteration.

So basically the only bug left is issue #2043; the corrupted values Andrei
reported seem to have been fixed since.

--