[Issue 12553] compilation fails if a forward referenced symbol represents a value and is first used as template parameter

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=12553

det <2k...@gmx.net> changed:

   What|Removed |Added

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

--- Comment #3 from det <2k...@gmx.net> ---
this issue seems to be fixed in DMD 2.071.1. example code now compiles w/o
errors.

--


[Issue 340] [Tracker] Forward reference bugs and other order-of-declaration issues

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=340
Issue 340 depends on issue 12553, which changed state.

Issue 12553 Summary: compilation fails if a forward referenced symbol 
represents a value and is first used as template parameter
https://issues.dlang.org/show_bug.cgi?id=12553

   What|Removed |Added

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

--


[Issue 15925] -transition=[check]imports ignores import declaration from mixin templates

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15925

det <2k...@gmx.net> changed:

   What|Removed |Added

   See Also||https://issues.dlang.org/sh
   ||ow_bug.cgi?id=16287

--


[Issue 16287] update mixin template specs to reflect new import rules (as of 2.071)

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16287

det <2k...@gmx.net> changed:

   What|Removed |Added

 CC||2k...@gmx.net
   See Also||https://issues.dlang.org/sh
   ||ow_bug.cgi?id=15925

--


[Issue 16287] New: update mixin template specs to reflect new import rules (as of 2.071)

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16287

  Issue ID: 16287
   Summary: update mixin template specs to reflect new import
rules (as of 2.071)
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P1
 Component: dlang.org
  Assignee: nob...@puremagic.com
  Reporter: 2k...@gmx.net

mixin template specs https://dlang.org/spec/template-mixin.html currently say:
"A TemplateMixin takes an arbitrary set of declarations from the body of a
TemplateDeclaration and inserts them into the current context."

as import declarations are declarations as well, this would make them available
to the current scope. indeed, this used to be the case until DMD 2.071, when
walter declared this behavior to be invalid:
https://issues.dlang.org/show_bug.cgi?id=15925#c5

now the documentation needs to be changed to explain that 
a) whole module imports (from the mixed in template) will not be visible in the
current scope
b) selective imports, however, will be visible in the current scope

--


[Issue 12735] imports via mixin template become public imports

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=12735

det <2k...@gmx.net> changed:

   What|Removed |Added

   See Also||https://issues.dlang.org/sh
   ||ow_bug.cgi?id=15925

--


[Issue 15925] -transition=[check]imports ignores import declaration from mixin templates

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15925

det <2k...@gmx.net> changed:

   What|Removed |Added

   See Also||https://issues.dlang.org/sh
   ||ow_bug.cgi?id=12735

--


[Issue 12735] imports via mixin template become public imports

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=12735

--- Comment #4 from det <2k...@gmx.net> ---
surprisingly, this issue is still not fixed in DMD 2.071.1. surprising, because
if the template would be mixed in the same module, the import would be
invisible.

--


[Issue 15900] [REG 2.071] (Import deprecation) Public import ignored when using fully qualified name

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15900

det <2k...@gmx.net> changed:

   What|Removed |Added

 CC||2k...@gmx.net

--


[Issue 15925] -transition=[check]imports ignores import declaration from mixin templates

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15925

--- Comment #15 from det <2k...@gmx.net> ---
having the status marked as RESOLVED FIXED is confusing at least - and i would
argue plain wrong. walter's post declared the original report as invalid, so it
has to be marked as such.

--


[Issue 15925] -transition=[check]imports ignores import declaration from mixin templates

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15925

det <2k...@gmx.net> changed:

   What|Removed |Added

 CC||2k...@gmx.net
 Resolution|FIXED   |INVALID

--


[Issue 13727] std.stdio.File not thread-safe

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13727

det <2k...@gmx.net> changed:

   What|Removed |Added

 CC||2k...@gmx.net

--


[Issue 16160] selective imports in aggregation shadow @property functions

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16160

det <2k...@gmx.net> changed:

   What|Removed |Added

 CC||2k...@gmx.net

--


[Issue 15907] Unjustified "is not visible from module" deprecation warning when using getMember trait

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15907

det <2k...@gmx.net> changed:

   What|Removed |Added

 CC||2k...@gmx.net

--


[Issue 16044] __traits(allMembers) returns empty tuple for subpackages

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16044

det <2k...@gmx.net> changed:

   What|Removed |Added

 CC||2k...@gmx.net

--


[Issue 16286] REG(2.071): Alias with 0 arguments gives: 'template std.meta.Alias does not match any template declaration'

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16286

Timothee Cour  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #1 from Timothee Cour  ---
nevermind, we are supposed to use AliasSeq instead of Alias

--


[Issue 16286] REG(2.071): Alias with 0 arguments gives: 'template std.meta.Alias does not match any template declaration'

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16286

Timothee Cour  changed:

   What|Removed |Added

 CC||timothee.co...@gmail.com
  Component|dmd |phobos

--


[Issue 16286] New: REG(2.071): Alias with 0 arguments gives: 'template std.meta.Alias does not match any template declaration'

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16286

  Issue ID: 16286
   Summary: REG(2.071): Alias with 0 arguments gives: 'template
std.meta.Alias does not match any template
declaration'
   Product: D
   Version: D2
  Hardware: x86
OS: Mac OS X
Status: NEW
  Severity: regression
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: timothee.co...@gmail.com

DMD64 D Compiler v2.071.1
dmd -c -o- main.d
Error: template std.meta.Alias does not match any template declaration

with dmd 2.070: ok


void fun(T...)(T args){
  import std.typetuple;
  // Error: template std.meta.Alias does not match any template declaration
  alias args2=Alias!(args);
  fun(args2);
}

void main(){
  fun();
  //fun(1);//ok
}



// bug_D20160717T115740

This regression makes generic code such as above painful, as it requires
special casing

--


[Issue 13537] Unions may break immutability

2016-07-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13537

Walter Bright  changed:

   What|Removed |Added

 CC||bugzi...@digitalmars.com

--- Comment #4 from Walter Bright  ---
Rebooted as:

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

--