Thread overview | |||||
---|---|---|---|---|---|
|
June 12 [Issue 24601] [next edition] Make opApply result opaque | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=24601 Bolpat <qs.il.paperinik@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 |P4 CC| |qs.il.paperinik@gmail.com -- |
June 12 [Issue 24601] [next edition] Make opApply result opaque | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=24601 Bolpat <qs.il.paperinik@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |safe --- Comment #1 from Bolpat <qs.il.paperinik@gmail.com> --- One reason is – and this is why I tagged this issue with safe – that it is unsafe to violate the opApply protocol. -- |
December 13 [Issue 24601] [next edition] Make opApply result opaque | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=24601 --- Comment #2 from dlangBugzillaToGithub <robert.schadek@posteo.de> --- THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/dmd/issues/20465 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB -- |
Copyright © 1999-2021 by the D Language Foundation