[Issue 18984] Debugging stack struct's which are returned causes incorrect debuginfo.
https://issues.dlang.org/show_bug.cgi?id=18984 --- Comment #4 from Manu --- This is closed right? --
[Issue 19011] New: visualD - not able to return to previous location after goto definition shortcut
https://issues.dlang.org/show_bug.cgi?id=19011 Issue ID: 19011 Summary: visualD - not able to return to previous location after goto definition shortcut Product: D Version: D2 Hardware: x86_64 OS: Windows Status: NEW Severity: enhancement Priority: P1 Component: visuald Assignee: nob...@puremagic.com Reporter: ben.stembri...@gmail.com After going to a definition of a function or variable (F12 - Edit.GotoDefinition) you are not able to return back to the previous location using other shortcuts (Ctrl+* View.BrowsePopContext or shift+F12 View.PopBrowseContext) Ive tried several versions of visual studio from 2017 down to 2005 --
[Issue 19010] New: new fails on dynamic array aliases
https://issues.dlang.org/show_bug.cgi?id=19010
Issue ID: 19010
Summary: new fails on dynamic array aliases
Product: D
Version: D2
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P1
Component: dmd
Assignee: nob...@puremagic.com
Reporter: elpenguin...@gmail.com
Pretty simple example:
```
unittest {
alias T = int[];
T t = new T;
}
```
This doesn't seem to have ever compiled correctly. It currently fails with the
misleading error "Error: new can only create structs, dynamic arrays or class
objects, not int[]'s"
--
[Issue 19009] core.internal.hash.hashOf default hash (absent `toHash`) should be `@nogc`
https://issues.dlang.org/show_bug.cgi?id=19009 --- Comment #1 from Nathan S. --- PR: https://github.com/dlang/druntime/pull/2228 --
[Issue 19009] New: core.internal.hash.hashOf default hash (absent `toHash`) should be `@nogc`
https://issues.dlang.org/show_bug.cgi?id=19009 Issue ID: 19009 Summary: core.internal.hash.hashOf default hash (absent `toHash`) should be `@nogc` Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P1 Component: druntime Assignee: nob...@puremagic.com Reporter: n8sh.second...@hotmail.com The default `hashOf` implementation used for types that do not have `toHash` uses `toUbyte` to get the byte representation which during CTFE requires allocation but during execution does not. The compiler currently takes CTFE-only code into account when inferring attributes but we can give it some help. --
[Issue 17067] D header file generation includes excess imports
https://issues.dlang.org/show_bug.cgi?id=17067
RazvanN changed:
What|Removed |Added
CC||razvan.nitu1...@gmail.com
--- Comment #1 from RazvanN ---
This is probably a WONTFIX since the header generation is done immediately
after the parsing phase so at that point no symbol resolution is done to see
which symbols come from which imports and the safe thing to do is to just put
them there; a workaround for this is to use scoped imports :
import std.stdio;
class Foo
{
void bar()
{
import std.stdio : writeln;
writeln("Hello world!");
}
}
--
[Issue 18969] 'need this for ' when passing field or method as template parameter
https://issues.dlang.org/show_bug.cgi?id=18969
--- Comment #1 from Simen Kjaeraas ---
Related:
import std.meta : Alias;
alias getMember(alias T, string name) = Alias!(__traits(getMember, T, name));
struct S {
int i = 0;
}
unittest {
S s;
getMember!(s, "i") = 2;
}
--
[Issue 18995] std.array.array doesn't free elements
https://issues.dlang.org/show_bug.cgi?id=18995 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --
[Issue 18995] std.array.array doesn't free elements
https://issues.dlang.org/show_bug.cgi?id=18995 --- Comment #3 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/4fe18b905526b4c1d0fb19aa28ccfcddf27ffcdc Fix issue 18995 - Make sure GC calls destructor when using std.array.array https://github.com/dlang/phobos/commit/db66b82b178480a636024371d76d016e6ee03971 Merge pull request #6584 from schveiguy/fix18995 Fix issue 18995 - Make sure GC calls destructor when using std.array.array merged-on-behalf-of: Petar Kirov --
