[Issue 14387] New: Disallow string literals as assert conditions

https://issues.dlang.org/show_bug.cgi?id=14387 Issue ID: 14387 Summary: Disallow string literals as assert conditions Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: enhancement

[Issue 14207] Assertion failure: '(vd-storage_class (STCout | STCref)) ? isCtfeReferenceValid(newval) : isCtfeValueValid(newval)' on line 6724 in file 'interpret.c'

https://issues.dlang.org/show_bug.cgi?id=14207 Nicolas Sicard dran...@gmail.com changed: What|Removed |Added Keywords||CTFE, ice

[Issue 12984] [REG2.068a] ICE on forward reference of derived class from other instantiated class

https://issues.dlang.org/show_bug.cgi?id=12984 --- Comment #5 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/D-Programming-Language/dmd https://github.com/D-Programming-Language/dmd/commit/302d42186a30452ddb0c7bd02f4f8c682a8f4c93 [Fix] Fix incorrect test for

[Issue 14388] Assertion failed: (type-ty != Tstruct || ((TypeStruct *)type)-sym == this)

https://issues.dlang.org/show_bug.cgi?id=14388 Nicolas Sicard dran...@gmail.com changed: What|Removed |Added Keywords||ice --

[Issue 14388] New: Assertion failed: (type-ty != Tstruct || ((TypeStruct *)type)-sym == this)

https://issues.dlang.org/show_bug.cgi?id=14388 Issue ID: 14388 Summary: Assertion failed: (type-ty != Tstruct || ((TypeStruct *)type)-sym == this) Product: D Version: D2 Hardware: x86_64 OS: All

[Issue 14388] ICE with idup-ed struct literal in template argument

https://issues.dlang.org/show_bug.cgi?id=14388 Kenji Hara k.hara...@gmail.com changed: What|Removed |Added Keywords||pull

[Issue 11080] assert(`string`) should be forbidden

https://issues.dlang.org/show_bug.cgi?id=11080 --- Comment #28 from Ketmar Dark ket...@ketmar.no-ip.org --- Created attachment 1505 -- https://issues.dlang.org/attachment.cgi?id=1505action=edit don't accept string as condition in `assert` and `static assert` --

[Issue 14391] New: Assigning to module results in unhelpful error message

https://issues.dlang.org/show_bug.cgi?id=14391 Issue ID: 14391 Summary: Assigning to module results in unhelpful error message Product: D Version: D2 Hardware: All OS: All Status: NEW Keywords: diagnostic

[Issue 14207] [REG2.065] Assertion failure: '(vd-storage_class (STCout | STCref)) ? isCtfeReferenceValid(newval) : isCtfeValueValid(newval)' on line 6724 in file 'interpret.c'

https://issues.dlang.org/show_bug.cgi?id=14207 Kenji Hara k.hara...@gmail.com changed: What|Removed |Added Keywords||pull Hardware|x86

[Issue 14389] The (attributelist): attribute notation scope of effect

https://issues.dlang.org/show_bug.cgi?id=14389 --- Comment #3 from Ketmar Dark ket...@ketmar.no-ip.org --- or simply introduce syntax to unattribute something. this is much more useful, imo, and not breaking any existing code. by the way: class C { private: @safe: void foo() {} public:

[Issue 14389] The (attributelist): attribute notation scope of effect

https://issues.dlang.org/show_bug.cgi?id=14389 --- Comment #4 from Ketmar Dark ket...@ketmar.no-ip.org --- p.s. the funny technical note: compiler has no mention of throw or impure functions (i.e. you can't set that flags by simply changing the parser). what compiler has is three states (for

[Issue 14305] DMD incorrectly interprets -of and -od with -lib

https://issues.dlang.org/show_bug.cgi?id=14305 --- Comment #2 from Temtaime temta...@gmail.com --- Seems that without -lib behavior is incorrect then. --

[Issue 14305] DMD incorrectly interprets -of and -od with -lib

https://issues.dlang.org/show_bug.cgi?id=14305 Temtaime temta...@gmail.com changed: What|Removed |Added CC||temta...@gmail.com --- Comment

[Issue 14305] DMD incorrectly interprets -of and -od with -lib

https://issues.dlang.org/show_bug.cgi?id=14305 --- Comment #3 from Vladimir Panteleev thecybersha...@gmail.com --- (In reply to Temtaime from comment #1) I think current behavior is correct. -od is not just for the output file, but also for intermediate files (.obj). -of should override -od for

[Issue 14389] New: The (attributelist): attribute notation scope of effect

https://issues.dlang.org/show_bug.cgi?id=14389 Issue ID: 14389 Summary: The (attributelist): attribute notation scope of effect Product: D Version: D2 Hardware: All OS: All Status: NEW

[Issue 14389] The (attributelist): attribute notation scope of effect

https://issues.dlang.org/show_bug.cgi?id=14389 Adam D. Ruppe destructiona...@gmail.com changed: What|Removed |Added CC|

[Issue 14390] New: [REG2.068a] ICE or bad has forward references error with circular class structure

https://issues.dlang.org/show_bug.cgi?id=14390 Issue ID: 14390 Summary: [REG2.068a] ICE or bad has forward references error with circular class structure Product: D Version: D2 Hardware: All OS: All

[Issue 14389] The (attributelist): attribute notation scope of effect

https://issues.dlang.org/show_bug.cgi?id=14389 --- Comment #2 from Daniel Čejchan czda...@gmail.com --- @Adam D. Ruppe:(In reply to Adam D. Ruppe from comment #1) class C { private: @safe: void foo() {} } Should foo still be private? I think a lot of people use this pattern