[Issue 5227] X ^^ FP at compile-time

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5227 Manu changed: What|Removed |Added Severity|enhancement |major --- Comment #6 from Manu --- Okay, so this has

[Issue 10556] mixin template fails overload resolution

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=10556 Ferdinand Majerech changed: What|Removed |Added CC||kiithsa...@gmail.com --- Comment #2 fro

[Issue 13905] calls to mutable methods are just ignored when instance is an enum

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13905 Andrej Mitrovic changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 13904] calls to mutable methods are just ignored when instance is an enum

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13904 --- Comment #1 from Andrej Mitrovic --- *** Issue 13905 has been marked as a duplicate of this issue. *** --

[Issue 5227] X ^^ FP at compile-time

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5227 safety0ff.bugz changed: What|Removed |Added CC||iteronve...@gmail.com --- Comment #5 from sa

[Issue 8562] math.pow fails at compile-time

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=8562 safety0ff.bugz changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 13840] [REG2.067a] nothrow attribute affects inside of try-catch block when using foreach with opApply

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13840 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/D-Programming-Language/dmd https://github.com/D-Programming-Language/dmd/commit/9bf5fb4d7c86085aa6b02e678f97f3dc85a99b40 fix Issue 13840 - nothrow at

[Issue 5227] X ^^ FP at compile-time

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5227 --- Comment #3 from safety0ff.bugz --- *** Issue 12946 has been marked as a duplicate of this issue. *** --

[Issue 5227] X ^^ FP at compile-time

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5227 safety0ff.bugz changed: What|Removed |Added CC||turkey...@gmail.com --- Comment #2 from safe

[Issue 5227] X ^^ FP at compile-time

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5227 safety0ff.bugz changed: What|Removed |Added CC||thecybersha...@gmail.com --- Comment #4 from

[Issue 13917] Can't use '^^' at compile time?!

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13917 safety0ff.bugz changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 12412] std.math.isNaN is not available during CTFE

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=12412 safety0ff.bugz changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 12946] Problems with floating point ^^ at compile time

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=12946 safety0ff.bugz changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 5227] X ^^ FP at compile-time

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5227 safety0ff.bugz changed: What|Removed |Added CC||safety0ff.b...@gmail.com See Also|

[Issue 3749] cannot evaluate yl2x (log) and exp functions at compile time

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=3749 safety0ff.bugz changed: What|Removed |Added See Also||https://issues.dlang.org/sh

[Issue 3749] cannot evaluate yl2x (log) and exp functions at compile time

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=3749 safety0ff.bugz changed: What|Removed |Added CC||safety0ff.b...@gmail.com --- Comment #19 fro

[Issue 13810] ICE in e2ir does not assert

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13810 --- Comment #4 from Steven Schveighoffer --- Most definitely. What happens now is: 1. Error: e2ir: cannot convert ... 2. Person says, "Oh, OK" fixes code. 3. person *maybe* files a bug report about a "stray e2ir" message. The error printout would h

[Issue 13871] [REG2.067a] Segmentation fault from std/variant.d:609

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13871 --- Comment #5 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/D-Programming-Language/phobos https://github.com/D-Programming-Language/phobos/commit/2e69efed7eae065f8b76fac2f1465fbf8fd7e977 fix Issue 13871 - Segm

[Issue 13810] ICE in e2ir does not assert

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13810 --- Comment #3 from yebblies --- (In reply to Steven Schveighoffer from comment #2) > OK, but do you agree with the assessment? > > I think at the very least the error message should say ICE. Right now, it > looks exactly the same as the error shoul

[Issue 13840] [REG2.067a] nothrow attribute affects inside of try-catch block when using foreach with opApply

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13840 Kenji Hara changed: What|Removed |Added Summary|nothrow attribute affects |[REG2.067a] nothrow |inside o

[Issue 13871] [REG2.067a] Segmentation fault from std/variant.d:609

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13871 Kenji Hara changed: What|Removed |Added Keywords||pull, wrong-code Hardware|x86_64

[Issue 13919] New: typeof(T.init[].front.init) crashes compiler for T = std.container.Array!int

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13919 Issue ID: 13919 Summary: typeof(T.init[].front.init) crashes compiler for T = std.container.Array!int Product: D Version: D2 Hardware: x86_64 OS: Linux

[Issue 13810] ICE in e2ir does not assert

2014-12-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13810 --- Comment #2 from Steven Schveighoffer --- OK, but do you agree with the assessment? I think at the very least the error message should say ICE. Right now, it looks exactly the same as the error should look, with the addition of e2ir. --