[Issue 18472] New: betterC: cannot use format at compile time.

2018-02-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18472 Issue ID: 18472 Summary: betterC: cannot use format at compile time. Product: D Version: D2 Hardware: x86 OS: All Status: NEW Severity: regression

[Issue 17353] is expression type specialization matching strips const

2018-02-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17353 uplink.co...@googlemail.com changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 8295] Struct member destructor can not be called from shared struct instance

2018-02-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=8295 --- Comment #12 from anonymous4 --- (In reply to Marco Leise from comment #10) > You can tell where I'm going: Copy a shared reference counting struct and it > is no longer shared except for the data it references. If you

[Issue 18468] cannot use `synchronized {}` in @safe code

2018-02-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18468 Seb changed: What|Removed |Added Keywords||pull CC|

[Issue 18468] cannot use `synchronized {}` in @safe code

2018-02-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18468 --- Comment #1 from Nicholas Wilson --- Im an idiot and can't read, still this should work. --

[Issue 18468] New: cannot use `synchronized {}` in @safe code

2018-02-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18468 Issue ID: 18468 Summary: cannot use `synchronized {}` in @safe code Product: D Version: D2 Hardware: x86 OS: Mac OS X Status: NEW Severity: enhancement

[Issue 18469] New: [REG 2.079-b1] Segfault when trying to get type of __dtor.opCall

2018-02-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18469 Issue ID: 18469 Summary: [REG 2.079-b1] Segfault when trying to get type of __dtor.opCall Product: D Version: D2 Hardware: All OS: All Status: NEW

[Issue 18034] SIMD optimization issues

2018-02-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18034 bitter.ta...@gmx.com changed: What|Removed |Added CC||bitter.ta...@gmx.com --- Comment #1

[Issue 18469] [REG 2.079-b1] Segfault when trying to get type of __dtor.opCall

2018-02-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18469 bitter.ta...@gmx.com changed: What|Removed |Added CC||bitter.ta...@gmx.com --- Comment #1

[Issue 18341] Documentation for std.array.split is confusing/incorrect

2018-02-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18341 Seb changed: What|Removed |Added Keywords||pull CC|

[Issue 18471] New: std.experimental.checkedint.Checked doesn't check on assignment or construction

2018-02-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18471 Issue ID: 18471 Summary: std.experimental.checkedint.Checked doesn't check on assignment or construction Product: D Version: D2 Hardware: x86 OS: Windows

[Issue 18470] New: std.algorithm.splitter has frame access problems for custom preds

2018-02-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18470 Issue ID: 18470 Summary: std.algorithm.splitter has frame access problems for custom preds Product: D Version: D2 Hardware: All OS: All Status: NEW

[Issue 18469] [REG 2.079-b1] Segfault when trying to get type of __dtor.opCall

2018-02-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18469 Basile B. changed: What|Removed |Added Keywords||ice, pull --- Comment #2 from