[Issue 23630] Regression in library caused by dmd 2.101.0 update
https://issues.dlang.org/show_bug.cgi?id=23630 --- Comment #4 from lemp...@gmail.com --- Hello. Is it possible to solve this problem? Earlier you mentioned that you used git bisect for troubleshooting. Is it possible to investigate and fix it locally for me in the same way? I would like to know the procedure if possible. Any other additional information or assistance I can provide? --
[Issue 23658] .di generation of variables should turn them into declarations
https://issues.dlang.org/show_bug.cgi?id=23658 Walter Bright changed: What|Removed |Added See Also||https://issues.dlang.org/sh ||ow_bug.cgi?id=4071 --
[Issue 4071] Missing support to share memory and objects between DLLs and executable
https://issues.dlang.org/show_bug.cgi?id=4071 Walter Bright changed: What|Removed |Added See Also||https://issues.dlang.org/sh ||ow_bug.cgi?id=23658 --
[Issue 23658] .di generation of variables should turn them into declarations
https://issues.dlang.org/show_bug.cgi?id=23658 --- Comment #2 from Walter Bright --- See also: https://github.com/dlang/dmd/pull/14849 --
[Issue 23300] std.array : array wrongly propagates scopeness of source
https://issues.dlang.org/show_bug.cgi?id=23300 johanenge...@weka.io changed: What|Removed |Added Keywords||industry --
[Issue 23294] [dip1000] parameter to parameter assignment leads to incorrect scope inference
https://issues.dlang.org/show_bug.cgi?id=23294 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #1 from Dlang Bot --- @dkorpel updated dlang/dmd pull request #14492 "Fix 20674, 23208, 23300 - improve `scope` inference" fixing this issue: - Fix 20674, 23208, 23300, 23294 - improve `scope` inference https://github.com/dlang/dmd/pull/14492 --
[Issue 23208] [dip1000] missing return scope inference after parameter assignment
https://issues.dlang.org/show_bug.cgi?id=23208 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #1 from Dlang Bot --- @dkorpel updated dlang/dmd pull request #14492 "Fix 20674, 23208, 23300 - improve `scope` inference" fixing this issue: - Fix 20674, 23208, 23300, 23294 - improve `scope` inference https://github.com/dlang/dmd/pull/14492 --
[Issue 23300] std.array : array wrongly propagates scopeness of source
https://issues.dlang.org/show_bug.cgi?id=23300 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #7 from Dlang Bot --- @dkorpel updated dlang/dmd pull request #14492 "Fix 20674, 23208, 23300 - improve `scope` inference" fixing this issue: - Fix 20674, 23208, 23300, 23294 - improve `scope` inference https://github.com/dlang/dmd/pull/14492 --
[Issue 20674] [DIP1000] inference of `scope` is easily confused
https://issues.dlang.org/show_bug.cgi?id=20674 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #7 from Dlang Bot --- @dkorpel updated dlang/dmd pull request #14492 "Fix 20674, 23208, 23300 - improve `scope` inference" fixing this issue: - Fix 20674, 23208, 23300, 23294 - improve `scope` inference https://github.com/dlang/dmd/pull/14492 --
[Issue 23657] [REG2.101] Incorrect error escape reference to stack allocated value
https://issues.dlang.org/show_bug.cgi?id=23657
Dennis changed:
What|Removed |Added
Status|NEW |RESOLVED
CC||dkor...@live.nl
Resolution|--- |DUPLICATE
--- Comment #1 from Dennis ---
Reduced:
```
import std.algorithm: map;
import std.array: array;
struct SmallSet
{
ushort[13] keys;
auto items() return { return keys[]; }
}
public struct RA {
SmallSet members() { return SmallSet(); }
}
RA agent;
auto foo() {
return agent.members.items.map!(x => x).array;
}
```
The problem is that members.items returns a slice to a local variable, which
should be okay because you call `array` in the end, but there you hit Issue
23300.
*** This issue has been marked as a duplicate of issue 23300 ***
--
[Issue 23300] std.array : array wrongly propagates scopeness of source
https://issues.dlang.org/show_bug.cgi?id=23300 Dennis changed: What|Removed |Added CC||johanenge...@weka.io --- Comment #6 from Dennis --- *** Issue 23657 has been marked as a duplicate of this issue. *** --
[Issue 23655] __traits(toType) shatters modularity
https://issues.dlang.org/show_bug.cgi?id=23655 --- Comment #2 from Adam D. Ruppe --- It should really just be removed from the language, as it serves no purpose and opens up a massive can of worms. --
