[Issue 18153] deprecate public symbols ByLine, ByRecord, ByChunk

https://issues.dlang.org/show_bug.cgi?id=18153 Seb changed: What|Removed |Added Keywords||pull Assignee|nob...@puremagic.com|g

[Issue 18115] [REG2.078-b1] case where && is not shortcut anymore in CTFE

https://issues.dlang.org/show_bug.cgi?id=18115 --- Comment #14 from Rainer Schuetze --- The problem here is not the short-circuiting of semantic analysis, but the const-folding now done on the second operand of "&&" that predicts a runtime error if the code is actually executed. Maybe it's ok to

[Issue 18152] std.format.formattedRead should work with rvalues.

https://issues.dlang.org/show_bug.cgi?id=18152 --- Comment #2 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/146306a27b80c407d619a4aa8aa44f8fc562e343 Fix Issue 18152 - Make std.format.formattedRead usable wi

[Issue 18152] std.format.formattedRead should work with rvalues.

https://issues.dlang.org/show_bug.cgi?id=18152 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|-

[Issue 18152] std.format.formattedRead should work with rvalues.

https://issues.dlang.org/show_bug.cgi?id=18152 hst...@quickfur.ath.cx changed: What|Removed |Added Summary|std.format.formatteedRead |std.format.formattedRead

[Issue 18152] std.format.formatteedRead should work with rvalues.

https://issues.dlang.org/show_bug.cgi?id=18152 hst...@quickfur.ath.cx changed: What|Removed |Added Keywords||pull --- Comment #1 from hst...@quic

[Issue 18152] New: std.format.formatteedRead should work with rvalues.

https://issues.dlang.org/show_bug.cgi?id=18152 Issue ID: 18152 Summary: std.format.formatteedRead should work with rvalues. Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: enhancement

[Issue 18115] [REG2.078-b1] case where && is not shortcut anymore in CTFE

https://issues.dlang.org/show_bug.cgi?id=18115 Martin Nowak changed: What|Removed |Added CC||c...@dawg.eu --- Comment #13 from Martin Nowa

[Issue 9073] In manifest constant initializer, && and || should evaluate their operands lazily.

https://issues.dlang.org/show_bug.cgi?id=9073 Martin Nowak changed: What|Removed |Added Status|REOPENED|RESOLVED CC|

[Issue 18114] [Reg 2.078] regex performance regression

https://issues.dlang.org/show_bug.cgi?id=18114 Martin Nowak changed: What|Removed |Added CC||bugzi...@digitalmars.com, |

[Issue 18151] New: wrong auto ref lvalue inference for implicitly converted alias this parameters

https://issues.dlang.org/show_bug.cgi?id=18151 Issue ID: 18151 Summary: wrong auto ref lvalue inference for implicitly converted alias this parameters Product: D Version: D2 Hardware: All OS: All S

[Issue 13838] @safe by default

https://issues.dlang.org/show_bug.cgi?id=13838 Jack Stouffer changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 18048] std.bigint.toDecimalString is impure

https://issues.dlang.org/show_bug.cgi?id=18048 Jack Stouffer changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 17746] Improve BigInt memory usage

https://issues.dlang.org/show_bug.cgi?id=17746 --- Comment #3 from Jack Stouffer --- On the other hand, if the COW is to avoid issues in code like this ``` BigInt a = 10; BigInt b = a; ++a; assert(b == 10); ``` where b could end up equaling 11, can we just make opAssign and the this(T : BigInt

[Issue 17746] Improve BigInt memory usage

https://issues.dlang.org/show_bug.cgi?id=17746 --- Comment #2 from hst...@quickfur.ath.cx --- If the BigInt is const, then the best we can do is to create a new BigInt to hold the result of the operation, i.e., what BigInt does now. For the optimization to have significant benefits, we pretty muc

[Issue 9631] Error message not using fully qualified name when appropriate.

https://issues.dlang.org/show_bug.cgi?id=9631 --- Comment #19 from Nick Treleaven --- (In reply to Andrej Mitrovic from comment #5) > test.d(9): Error: function foo.test (S s) is not callable using argument > types (S) https://github.com/dlang/dmd/pull/7554 --

[Issue 9631] Error message not using fully qualified name when appropriate.

https://issues.dlang.org/show_bug.cgi?id=9631 Nick Treleaven changed: What|Removed |Added CC||timothee.co...@gmail.com --- Comment #18 fro

[Issue 16610] Error: function fun (Bar bar) is not callable using argument types (Bar)

https://issues.dlang.org/show_bug.cgi?id=16610 Nick Treleaven changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 17746] Improve BigInt memory usage

https://issues.dlang.org/show_bug.cgi?id=17746 --- Comment #1 from Jack Stouffer --- >From my initial investigation into this, adding ref counting to BigInt is much more complicated than it first appears. Adding a size_t ref count on the heap for BigUint basically breaks the rest of BigInt becaus

[Issue 15613] Parameter type mismatch error message are not very helpful

https://issues.dlang.org/show_bug.cgi?id=15613 Nick Treleaven changed: What|Removed |Added CC||bearophile_h...@eml.cc --- Comment #4 from

[Issue 9056] More precise error messages when function arguments are wrong

https://issues.dlang.org/show_bug.cgi?id=9056 Nick Treleaven changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 16165] Better error message for mismatched function argument types

https://issues.dlang.org/show_bug.cgi?id=16165 Nick Treleaven changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE

<    1   2