[Issue 18669] isNestedFunction does not check if parameter is a function

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18669

github-bugzi...@puremagic.com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--


[Issue 18669] isNestedFunction does not check if parameter is a function

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18669

--- Comment #1 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/dlang/phobos

https://github.com/dlang/phobos/commit/09cc0bac145422636e88616ce88f8bab3f0adefc
Fix Issue 18669 - isNestedFunction does not check if parameter is a function

https://github.com/dlang/phobos/commit/a6afdef9320f9eb5ccd868928742c274d149a9f1
Merge pull request #6355 from JackStouffer/issue18669

Fix Issue 18669 - isNestedFunction does not check if parameter is a f…
merged-on-behalf-of: Jack Stouffer 

--


[Issue 18672] Error in @safe transitive propagation with associative arrays

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18672

Carsten Blüggel  changed:

   What|Removed |Added

 CC||chi...@posteo.net

--


[Issue 18197] [REG2.073] Internal error: backend\cgcod.c 1659

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18197

--- Comment #5 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/dlang/dmd

https://github.com/dlang/dmd/commit/689fa72cb110250bc8b0dc152e48e20ba1f67cf9
Fix issue 18197 - Correct optimization for OPpair in x87 mode

Attempting to push a non-fp value into mST0 results in a ICE.

https://github.com/dlang/dmd/commit/69ece8ca5b0bcaf290cfcb8a29c44048e9678284
Merge pull request #8082 from LemonBoy/b18197

Fix Issue 18197 - Correct optimization for OPpair in x87 mode
merged-on-behalf-of: Walter Bright 

--


[Issue 18197] [REG2.073] Internal error: backend\cgcod.c 1659

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18197

github-bugzi...@puremagic.com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--


[Issue 17874] Segmentation fault when constructing a struct with a static array of structs containing floats

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17874

github-bugzi...@puremagic.com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--


[Issue 17874] Segmentation fault when constructing a struct with a static array of structs containing floats

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17874

--- Comment #2 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/dlang/dmd

https://github.com/dlang/dmd/commit/5662aa94c091083f004530d7ed77ec42a93414a4
Fix issue 17874 - Static arrays & memset

Hopefully completes what #3784 started.

https://github.com/dlang/dmd/commit/161e2e038a656f8d849967821cb0c35a77386d32
Merge pull request #8092 from LemonBoy/b17874

Fix issue 17874 - Static arrays & memset
merged-on-behalf-of: Walter Bright 

--


[Issue 18433] rdmd doesn't respect DFLAGS for its cache hash

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18433

--- Comment #3 from Seb  ---
https://github.com/dlang/tools/pull/343

--


[Issue 14855] -cov should ignore assert(0)

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14855

--- Comment #7 from hst...@quickfur.ath.cx ---
To me it doesn't make sense that `assert(0);` should be counted towards
coverage.  I mean, `assert(0);` is basically the programmer telling the
compiler "this is not supposed to happen" and "this is unreachable code",
meaning that if execution ever gets to this point, the code is wrong and the
program is in an invalid state.  On the flip side, if everything else except
assert(0) were reached during execution, then surely that means the code is
100% covered, since the assert(0)'s are not supposed to ever happen, from the
language's POV.

--


[Issue 14855] -cov should ignore assert(0)

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14855

hst...@quickfur.ath.cx changed:

   What|Removed |Added

 CC||hst...@quickfur.ath.cx

--


[Issue 18433] rdmd doesn't respect DFLAGS for its cache hash

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18433

--- Comment #2 from Seb  ---
Argh, apparently this hasn't been fixed in master and DFLAGS is only looked at
when -conf= is set:

```
> DFLAGS="-version=Foo" ../dmd/generated/linux/release/64/dmd -v foo.d && ./foo
predefs   DigitalMars Posix linux ELFv1 LittleEndian D_Version2 all D_SIMD
D_InlineAsm_X86_64 X86_64 CRuntime_Glibc D_LP64 D_PIC assert D_HardFloat
binary../dmd/generated/linux/release/64/dmd
version   v2.079.0-284-g23b2e2e0d
config../dmd/generated/linux/release/64/dmd.conf
DFLAGS-I../dmd/generated/linux/release/64/../../../../../druntime/import
-I../dmd/generated/linux/release/64/../../../../../phobos
-L-L../dmd/generated/linux/release/64/../../../../../phobos/generated/linux/release/64
-L--export-dynamic -fPIC
```


```
> DFLAGS="-version=Foo" dmd -conf= -I~/dlang/phobos -I~/dlang/druntime/import 
> -c -v foo.d
predefs   Foo DigitalMars Posix linux ELFv1 LittleEndian D_Version2 all D_SIMD
D_InlineAsm_X86_64 X86_64 CRuntime_Glibc D_LP64 D_PIC assert D_HardFloat
binary/home/seb/dlang/dmd/generated/linux/release/64/dmd
version   v2.079.0-284-g23b2e2e0d
config
DFLAGS-version=Foo
```

--


[Issue 17874] Segmentation fault when constructing a struct with a static array of structs containing floats

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17874

Walter Bright  changed:

   What|Removed |Added

 CC||bugzi...@digitalmars.com

--- Comment #1 from Walter Bright  ---
https://github.com/dlang/dmd/pull/8092

--


[Issue 18433] rdmd doesn't respect DFLAGS for its cache hash

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18433

Seb  changed:

   What|Removed |Added

 CC||greensunn...@gmail.com
Summary|rdmd ignores DFLAGS |rdmd doesn't respect DFLAGS
   ||for its cache hash

--- Comment #1 from Seb  ---
Hmm I think the problem is more in DMD not respecting everything from DFLAGS:
However, this has been in master:

cat > foo.d << EOF
void main(){
import std.stdio;
version(Foo)
{
"foo".writeln;
}
else
{
"bar".writeln;
}
}
EOF


```
> dmd -version=Foo foo.d && ./foo
foo
> DFLAGS="-version=Foo" dmd foo.d && ./foo
bar
> DFLAGS="-version=Foo" rdmd --force foo.d
bar
```

(with ~master this correctly yields foo for all commands)

But it looks like rdmd's caching doesn't include a hash of DFLAGS.

```
DFLAGS="-version=Foo" rdmddev foo.d
foo
DFLAGS="-version=Bar" rdmddev foo.d
foo
```

(so I'm renaming this)

--


[Issue 10550] Xorshift32 and Xorshift160 do not generate uniformly-distributed random numbers

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=10550

Zach Bjornson  changed:

   What|Removed |Added

 CC||zbbjorn...@gmail.com

--- Comment #17 from Zach Bjornson  ---
I know this is an old bug, but for the sake of tying up loose ends:

The 13,17,5 triple is valid: On the bottom of page 2 [1], Marsaglia says "Of
those 81 triples with a < c, the triple (c, b, a) also provides a full period
T...". The triple 5,17,13 appears in the 32-bit table, so 13,17,5 is valid.

The triple used in the commit in this issue (13,17,15) is also valid, but was
an unnecessary change. The fix to add the xor was necessary.

[1] http://www.jstatsoft.org/v08/i14/paper

--


[Issue 17493] nothrow constructor may throw

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17493

Seb  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from Seb  ---
(accidentally reopened - sorry)

--


[Issue 17493] nothrow constructor may throw

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17493

--- Comment #4 from Walter Bright  ---
Why was this reopened?

--


[Issue 18672] Error in @safe transitive propagation with associative arrays

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18672

ag0aep6g  changed:

   What|Removed |Added

 CC||ag0ae...@gmail.com

--- Comment #2 from ag0aep6g  ---
(In reply to Seb from comment #1)
> So DMD already does transitively apply @safe, but apparently if it generated
> for associative arrays this generation doesn't work in all cases.

It's not the associative array. It's just that the generated opAssign isn't
@safe (for no reason):


void main() @safe
{
struct ThrowingElement
{
~this() {}
}

ThrowingElement aa;
/* Accepted. The destructor is apparently inferred as @safe. */
aa = aa;
/* Error: @safe function D main cannot call @system generated
function onlineapp.main.ThrowingElement.opAssign */
}


--


[Issue 18670] compiler segfault if `new` on a union type with dip1000

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18670

--- Comment #3 from hst...@quickfur.ath.cx ---
P.S. Tested on git commit 2e21d0713babf760e4428d6404d733282ef85e8a, just to be
clear.

--


[Issue 18670] compiler segfault if `new` on a union type with dip1000

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18670

--- Comment #2 from hst...@quickfur.ath.cx ---
Unable to reproduce problem on git master.  Perhaps it has since been fixed?

--


[Issue 18670] compiler segfault if `new` on a union type with dip1000

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18670

hst...@quickfur.ath.cx changed:

   What|Removed |Added

   Keywords||ice
 CC||hst...@quickfur.ath.cx
   Severity|major   |critical

--- Comment #1 from hst...@quickfur.ath.cx ---
This is an ICE; upping priority.

--


[Issue 18672] Error in @safe transitive propagation with associative arrays

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18672

hst...@quickfur.ath.cx changed:

   What|Removed |Added

 CC||hst...@quickfur.ath.cx

--


[Issue 18603] Illegal instruction: 4 on Mac OS 10.7.5 Leopard

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18603

--- Comment #6 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/dlang/installer

https://github.com/dlang/installer/commit/427674142aecdd820a017c73b75508d4cddb1dfe
Fix Issue 18603 - Illegal instruction: 4 on Mac OS 10.7.5 Leopard

https://github.com/dlang/installer/commit/47830a15d1a576b683c92b4bb4adc4a1d83a2b5d
Merge pull request #308 from wilzbach/fix-18603

Fix Issue 18603 - Illegal instruction: 4 on Mac OS 10.7.5 Leopard

--


[Issue 18672] Error in @safe transitive propagation with associative arrays

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18672

Seb  changed:

   What|Removed |Added

Summary|@safe should be |Error in @safe transitive
   |transitively propagated |propagation with
   ||associative arrays
   Severity|enhancement |normal

--- Comment #1 from Seb  ---
Argh I accidentally hit submit.

The reason for the resubmission is that the following code compiles fine
already:

cat > main.d << EOF
void main() @safe
{
struct Foo
{
int i;
~this() // <- no need to annotate with @safe explicitly here
{
assert(1);
}
void m(){}  // <- no need to annotate with @safe explicitly here
}

Foo foo;
foo.m();
}
EOF

So DMD already does transitively apply @safe, but apparently if it generated
for associative arrays this generation doesn't work in all cases.

--


[Issue 18672] New: @safe should be transitively propagated

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18672

  Issue ID: 18672
   Summary: @safe should be transitively propagated
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Keywords: safe
  Severity: enhancement
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: greensunn...@gmail.com

cat > main.d << EOF
void main() @safe
{
struct ThrowingElement
{
int i;
~this()
{
assert(1);
}
}

ThrowingElement[int] aa;
aa[0] = ThrowingElement(0);
}
EOF


(resubmission of the example of #18592 as I do believe that the compiler should

--


[Issue 18663] std.random.isSeedable has false positives

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18663

github-bugzi...@puremagic.com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--


[Issue 18663] std.random.isSeedable has false positives

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18663

--- Comment #2 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/dlang/phobos

https://github.com/dlang/phobos/commit/e9f56ba3b293670b7b7173ae75bf465448fff7ac
Fix Issue 18663 - std.random.isSeedable has false positives

https://github.com/dlang/phobos/commit/6400ada30fc296daef439535aea5b5b0ede6a3a0
Merge pull request #6348 from n8sh/isSeedable-fix

Fix Issue 18663 - std.random.isSeedable has false positives
merged-on-behalf-of: Jack Stouffer 

--


[Issue 18671] New: Implement loop unrolling in dmd's optimizer

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18671

  Issue ID: 18671
   Summary: Implement loop unrolling in dmd's optimizer
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: enhancement
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: hst...@quickfur.ath.cx

It has been known for a while that dmd's optimizer tends to lag behind
gdc/ldc's when it comes to the performance of the generated code.  While this
may give the appearance of general poor quality of the optimizer, closer
inspection reveals that actually dmd's optimizer does perform many standard
optimization operations, and arguably pretty well at it (it even performs code
hoisting from loops, for example). One big reason it fails to generate code
with performance competitive with ldc/gdc is because, as Walter himself said,
it doesn't unroll loops.

When it comes to optimization, there is often a domino effect where one
optimization leads to opportunities for further optimizations, whereas if that
first optimization wasn't performed, it also closes the door to subsequent
optimizations.  Loops being generally the locus of most performance-sensitive
code means that loop optimizations are especially sensitive to this effect, and
loop unrolling is an important step that could often lead to further
optimization opportunities.  Missing this step is a big reason why dmd's
optimizer often doesn't produce competitive code over ldc/gdc.

This has been talked about often, but it's about time it's logged as a real
request so that it won't be forgotten (and, one hopes, the chances of it
actually being implemented might increase just a tad further away from zero).

tl;dr: please implement loop unrolling in dmd. ;-)

--


[Issue 18184] std.zip should be usable in @safe

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18184

--- Comment #1 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/dlang/phobos

https://github.com/dlang/phobos/commit/a67d667d8b4234be99dc9ffde901dc88825153fb
Work On Issue 18184 - std.zip should be usable in @safe

https://github.com/dlang/phobos/commit/4ad1477bab05511c79508d49af9e74a6fd3b3147
Merge pull request #6254 from JackStouffer/issue18184

Work On Issue 18184 - std.zip should be usable in @safe
merged-on-behalf-of: Jack Stouffer 

--


[Issue 18550] Offline option for dlang.org makefile

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18550

--- Comment #4 from hst...@quickfur.ath.cx ---
Argh, is there a way to tell the `phobos-prerelease` target to just use the
local dmd repo instead of yet another remote cloning?

--


[Issue 18550] Offline option for dlang.org makefile

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18550

--- Comment #3 from hst...@quickfur.ath.cx ---
Thanks for taking the time to clarify.

I simply assumed it was downloading old releases because it needed to generate
tarballs and whatnot.  I've been on git master for too long, I don't even know
which official release we're on anymore. :-D

Is there any way to direct it to use the locally cloned and already-built dmd
instead?  I mean, it seems a little excessive to have to separately clone the
dmd repo when I already have one on hand.

Also, is the DIFFABLE=1 thing documented anywhere?  I admit I didn't look very
hard, I was just using the plain `html` target out of years of habit.

Anyway, the system incompatibility seems to have gone away with the latest git
pull.  I don't know if it was an actual incompatibility, or if it was caused by
dub not liking it when I interrupt it with ctrl-C and then try to rebuild again
afterwards, or something like that.  (I know it shouldn't be a problem, but
sometimes these things do happen.)

Basically, I would like to have the option of being able to build docs without
network access.

--


[Issue 18670] New: compiler segfault if `new` on a union type with dip1000

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18670

  Issue ID: 18670
   Summary: compiler segfault if `new` on a union type with
dip1000
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: major
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: john.loughran.col...@gmail.com

Found while trying to compile Adam D. Ruppe's terminal-emulator, reduced with
dustmite and some manual work

% cat terminalemulator.d
void foo() {
new OVERLAPPED;
}

union OVERLAPPED {
uint OffsetHigh;
uint Pointer;
}
% gdb dmd
< ... blah blah ... >
(gdb) r terminalemulator.d -dip1000
< ... blah blah ... >
DMD v2.079.0-283-g2e21d0713-dirty DEBUG

Program received signal SIGSEGV, Segmentation fault.
0x0059f2bd in dmd.escape.escapeByValue(dmd.expression.Expression,
dmd.escape.EscapeByResults*) (er=0x7ffeca60, e=0x0) at dmd/escape.d:1293
1293e.accept(v);
(gdb) bt
#0  0x0059f2bd in dmd.escape.escapeByValue(dmd.expression.Expression,
dmd.escape.EscapeByResults*) (er=0x7ffeca60, e=0x0) at dmd/escape.d:1293
#1  0x0059e4a9 in dmd.escape.checkNewEscape(dmd.dscope.Scope*,
dmd.expression.Expression, bool) (gag=false, e=0x0, sc=0x7e274120) at
dmd/escape.d:592
#2  0x005b8342 in ExpressionSemanticVisitor::visit(NewExp*)
(this=0x7ffecf08, exp=0x7f6b53b0) at dmd/expressionsem.d:2363
#3  0x005a9ba6 in NewExp::accept(Visitor*) (this=0x7f6b53b0,
v=0x7ffecf08) at dmd/expression.d:4155
#4  0x005cc5ef in expressionSemantic(Expression*, Scope*)
(e=0x7f6b53b0, sc=0x7e274120) at dmd/expressionsem.d:9367
#5  0x0064f0cc in StatementSemanticVisitor::visit(ExpStatement*)
(this=0x7ffecfd8, s=0x7f6b5420) at dmd/statementsem.d:177
#6  0x00631a0e in ExpStatement::accept(Visitor*) (this=0x7f6b5420,
v=0x7ffecfd8) at dmd/statement.d:715
#7  0x0064efa7 in statementSemantic(Statement*, Scope*)
(s=0x7f6b5420, sc=0x7e274120) at dmd/statementsem.d:126
#8  0x0064f38a in StatementSemanticVisitor::visit(CompoundStatement*)
(this=0x7ffed2d8, cs=0x7f6b5440) at dmd/statementsem.d:235
#9  0x00632206 in CompoundStatement::accept(Visitor*)
(this=0x7f6b5440, v=0x7ffed2d8) at dmd/statement.d:908
#10 0x0064efa7 in statementSemantic(Statement*, Scope*)
(s=0x7f6b5440, sc=0x7e274120) at dmd/statementsem.d:126
#11 0x00663aae in Semantic3Visitor::visit(FuncDeclaration*)
(this=0x7ffedb80, funcdecl=0x7f6b5060) at dmd/semantic3.d:581
#12 0x005d35e6 in FuncDeclaration::accept(Visitor*)
(this=0x7f6b5060, v=0x7ffedb80) at dmd/func.d:2277
#13 0x006623c5 in semantic3(Dsymbol*, Scope*) (dsym=0x7f6b5060,
sc=0x7e273e30) at dmd/semantic3.d:82
#14 0x006627c6 in Semantic3Visitor::visit(Module*)
(this=0x7ffedc30, mod=0x7f6b4c00) at dmd/semantic3.d:193
#15 0x0055838e in Module::accept(Visitor*) (this=0x7f6b4c00,
v=0x7ffedc30) at dmd/dmodule.d:1322
#16 0x006623c5 in semantic3(Dsymbol*, Scope*) (dsym=0x7f6b4c00,
sc=0x0) at dmd/semantic3.d:82
#17 0x005fd1f7 in dmd.mars.tryMain(ulong, const(char)**)
(argv=0x7ffee958, argc=3) at dmd/mars.d:836
#18 0x005fe17b in D main () at dmd/mars.d:1098

--


[Issue 18669] New: isNestedFunction does not check if parameter is a function

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18669

  Issue ID: 18669
   Summary: isNestedFunction does not check if parameter is a
function
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P1
 Component: phobos
  Assignee: nob...@puremagic.com
  Reporter: j...@jackstouffer.com

import std.traits;

class Outer
{
class Inner
{
}
}

void main()
{
void fun(int i);
int i;
struct SS
{
int bar() { return i; }
}
static assert(isNestedFunction!(fun));
static assert(isNestedFunction!(SS));
static assert(isNestedFunction!(Outer.Inner));
}

--


[Issue 17749] Compilation error "shared method ~this is not callable using a non-shared object" on shared object

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17749

uplink.co...@googlemail.com changed:

   What|Removed |Added

 CC||uplink.co...@googlemail.com

--- Comment #2 from uplink.co...@googlemail.com ---
Please link to PR or commit that fixed it

--


[Issue 17749] Compilation error "shared method ~this is not callable using a non-shared object" on shared object

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17749

RazvanN  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||razvan.nitu1...@gmail.com
 Resolution|--- |FIXED

--- Comment #1 from RazvanN  ---
This was fixed in git HEAD (DMD64 D Compiler v2.079.0-218-g54ab04e). Closing as
fixed.

--


[Issue 18432] alias x = x where x is an imported symbol should result in an error

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18432

RazvanN  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #8 from RazvanN  ---
Fixed. See: https://github.com/dlang/dmd/pull/7954

--


[Issue 18481] demangling error in stacktrace

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18481

RazvanN  changed:

   What|Removed |Added

 CC||razvan.nitu1...@gmail.com

--- Comment #1 from RazvanN  ---
Is this still available or has it been fixed once 18480 was fixed?

--


[Issue 12229] Properly name DMD compiler versions

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=12229

Seb  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||greensunn...@gmail.com
 Resolution|--- |WONTFIX

--- Comment #3 from Seb  ---
> We should indeed remove VERSION from the repo

See e.g.

https://github.com/dlang/dmd/pull/6935

tl;dr: VERSION needs to be kept in the source tree e.g. in case someone
downloads the source tarball from GitHub.

-> closing this as WONTFIX

--


[Issue 17268] Build dub with dmd version that included in the release

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17268

Seb  changed:

   What|Removed |Added

 CC||greensunn...@gmail.com

--- Comment #1 from Seb  ---
Looking at the source
(https://github.com/dlang/installer/blob/master/create_dmd_release/create_dmd_release.d#L532),
it seems like this was done on purpose:


// build dub with stable (host) compiler, b/c it breaks
// too easily with the latest compiler, e.g. for nightlies

Though I agree that the released dub should use the freshly built Phobos.

--


[Issue 15910] Prevent mismatch of VERSION information in dmd releases

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15910

Seb  changed:

   What|Removed |Added

 CC||greensunn...@gmail.com

--- Comment #6 from Seb  ---
Since a few versions DMD use the statically stored VERSION

https://github.com/dlang/dmd/pull/6935
https://github.com/dlang/dmd/pull/6749

Did this solve your problem?

--


[Issue 10941] object.d not found when following Mac installation instructions

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=10941

Seb  changed:

   What|Removed |Added

 CC||greensunn...@gmail.com

--- Comment #2 from Seb  ---
A start: https://github.com/dlang/dlang.org/pull/2306

--


[Issue 2473] Linux system install instructions incorrect

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=2473

Seb  changed:

   What|Removed |Added

 CC||greensunn...@gmail.com

--- Comment #1 from Seb  ---
Even though it's way too late, a start:
https://github.com/dlang/dlang.org/pull/2306

--


[Issue 13665] binary release doesn't work on newer FreeBSD (10) versions

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13665

Seb  changed:

   What|Removed |Added

 CC||greensunn...@gmail.com

--- Comment #1 from Seb  ---
FWIW with 2.080, DMD will only officially support FreeBSD 11 as the older build
hosts have been dropped.

--


[Issue 13812] Windows installer doesn't include rdmd.exe

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13812

Seb  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||greensunn...@gmail.com
 Resolution|--- |FIXED

--- Comment #1 from Seb  ---
Looks like this was only a temporary problem and has been fixed in the mean
time.

--


[Issue 14847] Windows installer should have an option to install VS compiler

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14847

Seb  changed:

   What|Removed |Added

 CC||greensunn...@gmail.com

--- Comment #2 from Seb  ---
I think the newest version of the installer can now either download + install
the VC compiler or use the embedded LLB linker, so I guess this can be closed?

--


[Issue 16393] Move install.sh to a more stable machine

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16393

Seb  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Seb  ---
This has been fixed in the last months.

--


[Issue 13133] Using "git describe --abbrev=0 tag^" to obtain previous dmd may identify incorrect version

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13133

Seb  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||greensunn...@gmail.com
 Resolution|--- |FIXED

--- Comment #1 from Seb  ---
The issue still exists, but I'm not sure for what this would be useful.
There have been many changes over the last four years and a VERSION file is now
stored in the dmd repository which most likely is what you are looking for.

I'm closing this now due to inactivity, but please reopen if the underlying
problem still exists.

--


[Issue 13139] deb package depends on many X libraries (through xdg-utils)

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13139

Seb  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||greensunn...@gmail.com
 Resolution|--- |FIXED

--- Comment #2 from Seb  ---
The dmd package has now been split up in these groups:

dmd-compiler (command line compiler and rdmd)
dmd-tools (includes: dumpobj, obj2asm, ddemangle and dustmite)
dmd-doc (documentation, man pages and examples)
libphobos2-nn (shared library)
libphobos2-dev (static library, symlink to shared library, module sources and
pkg-config files)

and it looks like dman is no longer shipped (or only for dmd-doc), so I'm
closing this as resolved. Please reopen if this is still an issue for you.

--


[Issue 13264] 2.066-rc1 installer had problems

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13264

Seb  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||greensunn...@gmail.com
 Resolution|--- |FIXED

--- Comment #3 from Seb  ---
It looks like this has been resolved and it's 4 years later without an
activity, so I'm closing this. 
Please reopen if this issue still exists or simply report a new one. Thanks!

--


[Issue 14295] Create rpm and debian packages as part of the build process

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14295

Seb  changed:

   What|Removed |Added

 CC||greensunn...@gmail.com

--- Comment #1 from Seb  ---
The most interesting comment in this thread:

---
We could try to host an apt and yum repo on dlang.org.
Might be simple to do, but it's not much better than the deb/rpm download we
offer.
It only gets interesting when we could land DMD in official repos, volunteering
package maintainers are welcome and should please contact me.
I hope we can sort out the redistribution part of the backend somehow.

We should include the few commands to install the packages on the download
page.
---

Well, now that the DMD backend is Boost licensed too, there is nothing stopping
distros to ship DMD, but somehow they haven't done so.
Sociomantic plans to move d-apt to GitHub + Bintray:

https://github.com/orgs/dlang-community/teams/all/discussions/2

So maybe efforts for Ubuntu/Debian should focus on/collaborate with this.

--


[Issue 14636] Make dub part of the standard distribution for all platforms

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14636

Seb  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||greensunn...@gmail.com
 Resolution|--- |FIXED

--- Comment #2 from Seb  ---
DUB has been included in the official archives since 2.072

--


[Issue 14849] Visual Studio 2015 not detected during installation

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14849

Seb  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 CC||greensunn...@gmail.com
 Resolution|--- |FIXED

--- Comment #16 from Seb  ---
Closing as fixed as AFAIK this has been fixed for a long time now and there
have been many tweaks to the detection since.

If this problem still exists, please reopen or open a new issue. Thanks!

--


[Issue 15693] Peculiar problems with OSX archive

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15693

Seb  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||greensunn...@gmail.com
 Resolution|--- |FIXED

--- Comment #4 from Seb  ---
No problem here either and we use the OSX archive on many many OSX CIs (via
Travis).
As this issue is about 2.070 I'm assuming that of an issue really existed, it
has been fixed now -> closing

--


[Issue 18197] [REG2.073] Internal error: backend\cgcod.c 1659

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18197

Walter Bright  changed:

   What|Removed |Added

   Hardware|x86_64  |x86

--


[Issue 15758] .deb not installing on Ubuntu 15.10 since 2.7x was released.

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15758

Seb  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||greensunn...@gmail.com
 Resolution|--- |FIXED

--- Comment #1 from Seb  ---
I found this issue by going through old issues and it looks like this was a
temporary problem. Closing as fixed. Please reopen or open a new issue if this
problem still exists.

--


[Issue 18197] [REG2.073] Internal error: backend\cgcod.c 1659

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18197

--- Comment #4 from Walter Bright  ---
(In reply to Walter Bright from comment #3)
> (In reply to Rainer Schuetze from comment #1)
> > Corrected test case:
> 
> I cannot reproduce a failure. What dmd flags are you using?

Ah, I see. It is classified above as an x86_64 problem, but it is an x86
problem. The flags to repro it are:

   -m32 -O -inline

--