https://issues.dlang.org/show_bug.cgi?id=21929
a11e99z <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from a11e99z <[email protected]> --- agree with bug. man creating new delegate/lambda with new internal state. what is reason to store just one shared state for created multiple delegetes in loop? what is using case for it? if D-team don't want to break current behavior let add new keyword "lambda" that is 100% compatible with "delegate" but it grabs totally new state when created - just changed compile time generated code. C++ byRef & byValue capturing is more viable. --
