[Issue 18444] [DIP25][DIP1000] Tracking issue for: "The implementation doesn't match DIPs 25/1000"

https://issues.dlang.org/show_bug.cgi?id=18444 Issue 18444 depends on issue 17512, which changed state. Issue 17512 Summary: [REG 2.073] [DIP1000] Error on bad interplay of 'auto ref' and 'return' attribute deduction. https://issues.dlang.org/show_bug.cgi?id=17512 What|Removed

[Issue 18530] [Reg 2.079] src/rt/tracegc.d(43): Deprecation: The delete keyword has been deprecated

https://issues.dlang.org/show_bug.cgi?id=18530 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/95e86e960f6c93875c5a3b16f5edff343997290e fix Issue 18530 - src/rt/tracegc.d(43): Deprecation: The

[Issue 17512] [REG 2.073] [DIP1000] Error on bad interplay of 'auto ref' and 'return' attribute deduction.

https://issues.dlang.org/show_bug.cgi?id=17512 --- Comment #6 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/56b770c60cb301b46a287e201fb4934f6551414b fix Issue 17512 - [REG 2.073] [DIP1000] Error on bad

[Issue 18530] [Reg 2.079] src/rt/tracegc.d(43): Deprecation: The delete keyword has been deprecated

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

[Issue 18282] [Scope][DIP1000]Assignment of local variable to `scope` variable not recognized by compiler

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

[Issue 18282] [Scope][DIP1000]Assignment of local variable to `scope` variable not recognized by compiler

https://issues.dlang.org/show_bug.cgi?id=18282 --- Comment #5 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/ac0224287fd16d293081059acef7c23b94212a7b fix Issue 18282 - [Scope][DIP1000]Assignment of local

[Issue 18484] [dip1000] Subtype allows reference to escape with implicit casting

https://issues.dlang.org/show_bug.cgi?id=18484 --- Comment #3 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/ff6edd1f56da1604d0b22d5342c5100633551cce fix Issue 18484 - [dip1000] Subtype allows reference to

[Issue 18484] [dip1000] Subtype allows reference to escape with implicit casting

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

[Issue 18136] ICE in dmd/statement.d(426)

https://issues.dlang.org/show_bug.cgi?id=18136 greenify changed: What|Removed |Added CC||greeen...@gmail.com ---

[Issue 18620] New: `error cannot be interpreted at compile time` is missing context where error occurs

https://issues.dlang.org/show_bug.cgi?id=18620 Issue ID: 18620 Summary: `error cannot be interpreted at compile time` is missing context where error occurs Product: D Version: D2 Hardware: x86 OS: All

[Issue 18445] [DIP25][DIP1000] Wrong "return as a parameter attribute" inference

https://issues.dlang.org/show_bug.cgi?id=18445 Carsten Blüggel changed: What|Removed |Added Summary|[DIP25] |[DIP25][DIP1000] Wrong

[Issue 18172] std.getopt should allow taking parameters by `ref` (like std.format.formattedRead), s.t. it can be used in @safe

https://issues.dlang.org/show_bug.cgi?id=18172 --- Comment #9 from Seb --- > then I get linker errors about stuff in std.conv being undefined, but there > are no more errors from the compiler itself. I think that that happens > sometimes when some code is compiled with

[Issue 18172] std.getopt should allow taking parameters by `ref` (like std.format.formattedRead), s.t. it can be used in @safe

https://issues.dlang.org/show_bug.cgi?id=18172 --- Comment #8 from Jonathan M Davis --- (In reply to Jack Stouffer from comment #7) > I should have emphized more the fact that I had already modified getopt. > I've attached my changes as a patch Without compiling

[Issue 18282] [Scope][DIP1000]Assignment of local variable to `scope` variable not recognized by compiler

https://issues.dlang.org/show_bug.cgi?id=18282 Carsten Blüggel changed: What|Removed |Added CC||chi...@posteo.net --

[Issue 18596] std.random.unpredictableSeed could use something better than MinstdRand0

https://issues.dlang.org/show_bug.cgi?id=18596 --- Comment #1 from Nathan S. --- Pull request https://github.com/dlang/phobos/pull/6267 --

[Issue 18478] Spurious "escapes a reference to local variable" error in function that does not return by reference

https://issues.dlang.org/show_bug.cgi?id=18478 Carsten Blüggel changed: What|Removed |Added CC||chi...@posteo.net --

[Issue 18484] [dip1000] Subtype allows reference to escape with implicit casting

https://issues.dlang.org/show_bug.cgi?id=18484 Carsten Blüggel changed: What|Removed |Added CC||chi...@posteo.net --

[Issue 18174] std.math.equalsDigit should be usable in @safe

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

[Issue 18110] most of phobos should be @safe-ly useable

https://issues.dlang.org/show_bug.cgi?id=18110 Issue 18110 depends on issue 18174, which changed state. Issue 18174 Summary: std.math.equalsDigit should be usable in @safe https://issues.dlang.org/show_bug.cgi?id=18174 What|Removed |Added

[Issue 18174] std.math.equalsDigit should be usable in @safe

https://issues.dlang.org/show_bug.cgi?id=18174 --- Comment #1 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/a4d98d0e9091a24276d12a3914217e05fcb0b584 Fix Issue 18174 - std.math.equalsDigit should be usable

[Issue 18172] std.getopt should allow taking parameters by `ref` (like std.format.formattedRead), s.t. it can be used in @safe

https://issues.dlang.org/show_bug.cgi?id=18172 --- Comment #7 from Jack Stouffer --- (In reply to Jonathan M Davis from comment #5) > You have to compile with -dip1000, which Phobos isn't right now. If I try it > locally with -dip1000, I get > > q.d(10): Error: scope

[Issue 18172] std.getopt should allow taking parameters by `ref` (like std.format.formattedRead), s.t. it can be used in @safe

https://issues.dlang.org/show_bug.cgi?id=18172 Jack Stouffer changed: What|Removed |Added Attachment #1683|application/mbox|text/plain

[Issue 18172] std.getopt should allow taking parameters by `ref` (like std.format.formattedRead), s.t. it can be used in @safe

https://issues.dlang.org/show_bug.cgi?id=18172 --- Comment #6 from Jack Stouffer --- Created attachment 1683 --> https://issues.dlang.org/attachment.cgi?id=1683=edit getopt.patch --

[Issue 18172] std.getopt should allow taking parameters by `ref` (like std.format.formattedRead), s.t. it can be used in @safe

https://issues.dlang.org/show_bug.cgi?id=18172 --- Comment #5 from Jonathan M Davis --- You have to compile with -dip1000, which Phobos isn't right now. If I try it locally with -dip1000, I get q.d(10): Error: scope variable f assigned to non-scope parameter

[Issue 18172] std.getopt should allow taking parameters by `ref` (like std.format.formattedRead), s.t. it can be used in @safe

https://issues.dlang.org/show_bug.cgi?id=18172 --- Comment #4 from Jack Stouffer --- (In reply to Jonathan M Davis from comment #3) > I'd suggest looking into how DIP 1000 can fix this problem without needing > ref, since with DIP 1000, taking the address of a local

[Issue 18619] documented unittests extracted by test_extractor should be run by auto-tester

https://issues.dlang.org/show_bug.cgi?id=18619 --- Comment #3 from greenify --- (In reply to Timothee Cour from comment #2) > so if i understand correctly circleci runs the (unextracted) unittests > blocks (regardless of documented or not) and at the moment nothing (except >

[Issue 18619] documented unittests extracted by test_extractor should be run by auto-tester

https://issues.dlang.org/show_bug.cgi?id=18619 --- Comment #2 from Timothee Cour --- so if i understand correctly circleci runs the (unextracted) unittests blocks (regardless of documented or not) and at the moment nothing (except end user on dlang.org) runs the

[Issue 18619] documented unittests extracted by test_extractor should be run by auto-tester

https://issues.dlang.org/show_bug.cgi?id=18619 greenify changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 18488] test_extractor misses version(unittest) blocks, causing `Deprecation: X is not visible from Y`

https://issues.dlang.org/show_bug.cgi?id=18488 --- Comment #6 from Timothee Cour --- ok filed a bug for that so we don't forget: https://issues.dlang.org/show_bug.cgi?id=18619 --

[Issue 18619] New: documented unittests extracted by test_extractor should be run by auto-tester

https://issues.dlang.org/show_bug.cgi?id=18619 Issue ID: 18619 Summary: documented unittests extracted by test_extractor should be run by auto-tester Product: D Version: D2 Hardware: x86 OS: Mac OS X

[Issue 18619] documented unittests extracted by test_extractor should be run by auto-tester

https://issues.dlang.org/show_bug.cgi?id=18619 Timothee Cour changed: What|Removed |Added CC|

[Issue 18618] templated functions should in general have their attributes inferred

https://issues.dlang.org/show_bug.cgi?id=18618 Timothee Cour changed: What|Removed |Added CC|

[Issue 18618] New: templated functions should in general have their attributes inferred

https://issues.dlang.org/show_bug.cgi?id=18618 Issue ID: 18618 Summary: templated functions should in general have their attributes inferred Product: D Version: D2 Hardware: x86 OS: Mac OS X

[Issue 18488] test_extractor misses version(unittest) blocks, causing `Deprecation: X is not visible from Y`

https://issues.dlang.org/show_bug.cgi?id=18488 greenify changed: What|Removed |Added CC||greeen...@gmail.com ---

[Issue 18488] test_extractor misses version(unittest) blocks, causing `Deprecation: X is not visible from Y`

https://issues.dlang.org/show_bug.cgi?id=18488 --- Comment #4 from Timothee Cour --- > people have rightfully complained a lot about examples from the docs not > working locally in the past just curious, doesn't auto-tester make sure that the extracted documented

[Issue 18617] New: need __traits(deprecated, expr) to check whether an expression would trigger deprecation

https://issues.dlang.org/show_bug.cgi?id=18617 Issue ID: 18617 Summary: need __traits(deprecated, expr) to check whether an expression would trigger deprecation Product: D Version: D2 Hardware: x86 OS: Mac OS

[Issue 18617] need __traits(deprecated, expr) to check whether an expression would trigger deprecation

https://issues.dlang.org/show_bug.cgi?id=18617 Timothee Cour changed: What|Removed |Added OS|Mac OS X|All --

[Issue 18617] need __traits(deprecated, expr) to check whether an expression would trigger deprecation

https://issues.dlang.org/show_bug.cgi?id=18617 Timothee Cour changed: What|Removed |Added CC|

[Issue 18488] test_extractor misses version(unittest) blocks, causing `Deprecation: X is not visible from Y`

https://issues.dlang.org/show_bug.cgi?id=18488 --- Comment #3 from Seb --- > this seems not true anymore, so `version(unittest)` is ok again, see: Well, it's an open problem - it was reverted because with -deps ALL unittest blocks are compiled (even the ones in Phobos).

[Issue 18488] test_extractor misses version(unittest) blocks, causing `Deprecation: X is not visible from Y`

https://issues.dlang.org/show_bug.cgi?id=18488 Timothee Cour changed: What|Removed |Added CC|

[Issue 18554] `tupleof` ignoring `private` shouldn't be accepted in @safe code

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

[Issue 18554] `tupleof` ignoring `private` shouldn't be accepted in @safe code

https://issues.dlang.org/show_bug.cgi?id=18554 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/a070de9d094c41785d00e3ec906664c3b482d0af fix Issue 18554 - tupleof ignoring private shouldn't be

[Issue 18613] Documentation: recommended construction/destruction patterns for manual memory management

https://issues.dlang.org/show_bug.cgi?id=18613 --- Comment #2 from Manu --- He's interacting with existing C++ code, and doesn't want to have conflicting allocation strategies. It's gamedev, so custom allocation mechanisms are already in use. He did find the cpptod, read

[Issue 18610] dman missing in 2.079 Windows package

https://issues.dlang.org/show_bug.cgi?id=18610 --- Comment #2 from greenify --- See also: https://github.com/dlang/dlang.org/pull/2212 --

[Issue 18610] dman missing in 2.079 Windows package

https://issues.dlang.org/show_bug.cgi?id=18610 greenify changed: What|Removed |Added CC||greeen...@gmail.com

[Issue 18613] Documentation: recommended construction/destruction patterns for manual memory management

https://issues.dlang.org/show_bug.cgi?id=18613 greenify changed: What|Removed |Added CC||greeen...@gmail.com ---

[Issue 18616] New: attrib.h:31:7: warning: 'AttribDeclaration' has virtual functions but non-virtual destructor [-Wnon-virtual-dtor]

https://issues.dlang.org/show_bug.cgi?id=18616 Issue ID: 18616 Summary: attrib.h:31:7: warning: 'AttribDeclaration' has virtual functions but non-virtual destructor [-Wnon-virtual-dtor] Product: D Version: D2