[Issue 18954] extern(C++) ICE when `cppmangle` is used

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18954 --- Comment #4 from Mike Franklin --- I attempted to fix it, but couldn't reproduce it, so I don't know what needs to be fixed. --

[Issue 19068] __traits(identifier) returns the wrong string when importing a template from a module

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19068 Simen Kjaeraas changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 19011] visualD - not able to return to previous location after goto definition shortcut

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19011 Rainer Schuetze changed: What|Removed |Added CC||r.sagita...@gmx.de --- Comment #1 from Rai

[Issue 19066] [REG 2.080.1] Error: `const(Object)` is used as a type with structs that have symbol named Object

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19066 --- Comment #7 from Jacob Carlborg --- (In reply to Steven Schveighoffer from comment #6) > Oh, haha! I meant I'll try updating the compiler to use the fully qualified > name object.Object :) Yes, I did that. But now looking at your PR I see that I

[Issue 18954] extern(C++) ICE when `cppmangle` is used

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18954 --- Comment #3 from Manu --- I'm pretty sure nobody attempted to fix it...? --

[Issue 19068] New: __traits(identifier) returns the wrong string when importing a template from a module

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19068 Issue ID: 19068 Summary: __traits(identifier) returns the wrong string when importing a template from a module Product: D Version: D2 Hardware: x86_64 OS: Linux

[Issue 19066] [REG 2.080.1] Error: `const(Object)` is used as a type with structs that have symbol named Object

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19066 --- Comment #6 from Steven Schveighoffer --- Oh, haha! I meant I'll try updating the compiler to use the fully qualified name object.Object :) --

[Issue 19066] [REG 2.080.1] Error: `const(Object)` is used as a type with structs that have symbol named Object

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19066 --- Comment #5 from Steven Schveighoffer --- (In reply to Jacob Carlborg from comment #3) > I gave that a try, it resulted in a new error message: Not sure what you tried, but I found something that seems to work, at least locally. --

[Issue 19066] [REG 2.080.1] Error: `const(Object)` is used as a type with structs that have symbol named Object

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19066 Steven Schveighoffer changed: What|Removed |Added Keywords||pull, rejects-valid --- Comment #4 fr

[Issue 19066] [REG 2.080.1] Error: `const(Object)` is used as a type with structs that have symbol named Object

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19066 --- Comment #3 from Jacob Carlborg --- (In reply to Steven Schveighoffer from comment #1) > I'll try using the fully qualified type, and see if it fixes the issue. I gave that a try, it resulted in a new error message: Error: need `this` for `Obje

[Issue 19066] [REG 2.080.1] Error: `const(Object)` is used as a type with structs that have symbol named Object

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19066 Steven Schveighoffer changed: What|Removed |Added Summary|[REG 2.081.0] Error:|[REG 2.080.1] Error:

[Issue 19067] [Mixins] Dead Link to template-mixin

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19067 ag0aep6g changed: What|Removed |Added Keywords||pull CC|

[Issue 19066] [REG 2.081.0] Error: `const(Object)` is used as a type

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19066 Steven Schveighoffer changed: What|Removed |Added CC||schvei...@yahoo.com Assigne

[Issue 19057] 2.079 changelog variadic template and default arguments

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19057 --- Comment #12 from Steven Schveighoffer --- (In reply to Jonathan M Davis from comment #11) > Well, having file or line end up being given values just because a string or > string and integral value happened to be last in the argument list would >

[Issue 19067] New: [Mixins] Dead Link to template-mixin

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19067 Issue ID: 19067 Summary: [Mixins] Dead Link to template-mixin Product: D Version: D2 Hardware: All URL: http://dlang.org/ OS: All Status: NEW Sev

[Issue 19067] [Mixins] Dead Link to template-mixin

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19067 desi...@heidel.beer changed: What|Removed |Added URL|http://dlang.org/ |https://dlang.org/articles/

[Issue 18954] extern(C++) ICE when `cppmangle` is used

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18954 Mike Franklin changed: What|Removed |Added CC||slavo5...@yahoo.com --- Comment #2 from Mike

[Issue 7071] "final:" shouldn't affect variables

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=7071 --- Comment #6 from RazvanN --- If final is applied directly to the declaration, the compiler will issue an error: class C { final string s; // error: cannot apply final to variable declarations; } However, if final is used as in the original bu

[Issue 7071] "final:" shouldn't affect variables

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=7071 --- Comment #5 from Vladimir Panteleev --- BTW, is this bug even valid? What does "final" mean for a variable? Maybe refusing to compile "final" with variables is the correct behavior? If so, does that mean there's a regression? --

[Issue 7071] "final:" shouldn't affect variables

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=7071 Vladimir Panteleev changed: What|Removed |Added Resolution|FIXED |WORKSFORME --- Comment #4 from Vladimir

[Issue 7071] "final:" shouldn't affect variables

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=7071 RazvanN changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 19066] New: [REG 2.081.0] Error: `const(Object)` is used as a type

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19066 Issue ID: 19066 Summary: [REG 2.081.0] Error: `const(Object)` is used as a type Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: regression

[Issue 19058] __traits(getUnitTests) stops working with separate compilation in dmd 2.081.0

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19058 --- Comment #3 from Atila Neves --- I've taken a look at the code (I was trying to fix this). As mentioned before, counters can never work. The solution will have to go through using the absolute path of the location since the module doesn't "exist"

[Issue 19058] __traits(getUnitTests) stops working with separate compilation in dmd 2.081.0

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19058 --- Comment #2 from Atila Neves --- Just compile two files separately with a unittest on the same line and column and have a third import the two and use __traits(getUnitTests). My failing test case is adding another imported module to the existing t

[Issue 19056] UDAs can be added to imports but not retrieved

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19056 RazvanN changed: What|Removed |Added CC||razvan.nitu1...@gmail.com --- Comment #1 from Razv

[Issue 19065] Struct invariant violated in @safe with T.init

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19065 FeepingCreature changed: What|Removed |Added Severity|enhancement |normal --

[Issue 19065] New: Struct invariant violated in @safe with T.init

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19065 Issue ID: 19065 Summary: Struct invariant violated in @safe with T.init Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: enhancement

[Issue 19057] 2.079 changelog variadic template and default arguments

2018-07-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19057 --- Comment #11 from Jonathan M Davis --- (In reply to Steven Schveighoffer from comment #8) > I think we need to find a way to change this behavior, and soon. As it > stands now, it doesn't make sense, as it's only useful in the __FILE__ and > __LIN