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

https://issues.dlang.org/show_bug.cgi?id=18618 --- Comment #2 from Carsten Blüggel --- (In reply to Jonathan M Davis from comment #1) > Templated functions should have their attributes inferred when whether > attributes make sense depend on the template arguments (which the

[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 #7 from Walter Bright --- https://github.com/dlang/dmd/pull/8045 --

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

https://issues.dlang.org/show_bug.cgi?id=18618 Jonathan M Davis 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 Carsten Blüggel changed: What|Removed |Added CC||chi...@posteo.net --

[Issue 6138] Using dirEntries and chdir() can have unwanted results

https://issues.dlang.org/show_bug.cgi?id=6138 Timothee Cour changed: What|Removed |Added OS|Windows |All

[Issue 17772] Wrong C++ mangled names for templated functions

https://issues.dlang.org/show_bug.cgi?id=17772 Walter Bright changed: What|Removed |Added See Also|

[Issue 18582] C++ namespace mangling from multiple modules doesn't use sequence ids

https://issues.dlang.org/show_bug.cgi?id=18582 Walter Bright changed: What|Removed |Added See Also|

[Issue 18582] C++ namespace mangling from multiple modules doesn't use sequence ids

https://issues.dlang.org/show_bug.cgi?id=18582 Walter Bright changed: What|Removed |Added Keywords||betterC

[Issue 18622] New: Outdated information regarding link definition when generated by Visual D DLL project.

https://issues.dlang.org/show_bug.cgi?id=18622 Issue ID: 18622 Summary: Outdated information regarding link definition when generated by Visual D DLL project. Product: D Version: D2 Hardware: x86_64 OS:

[Issue 18198] @disable semantic not applied for the delete operator

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

[Issue 18129] Function parameter 'scope' does not mean without @safe

https://issues.dlang.org/show_bug.cgi?id=18129 --- Comment #5 from John Hall --- Ah, you're right. It says "Errors for scope violations are only reported in @safe code." --

[Issue 18129] Function parameter 'scope' does not mean without @safe

https://issues.dlang.org/show_bug.cgi?id=18129 --- Comment #4 from Jonathan M Davis --- As I understand it, -dip1000 has no effect on code that isn't @safe. So, you're not going to have the compiler yelling at you over it if you're not using @safe. Either way,

[Issue 18129] Function parameter 'scope' does not mean without @safe

https://issues.dlang.org/show_bug.cgi?id=18129 --- Comment #3 from John Hall --- Jonathan, I was a little hesitant to say I was sure it was a duplicate of that one because I tried running it on run.dlang.org with the -dip1000 flag and it was still not giving a

[Issue 6931] scope parameter storage class not checked at all

https://issues.dlang.org/show_bug.cgi?id=6931 Jonathan M Davis changed: What|Removed |Added CC|

[Issue 18129] Function parameter 'scope' does not mean without @safe

https://issues.dlang.org/show_bug.cgi?id=18129 Jonathan M Davis changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 18129] Function parameter 'scope' does not mean without @safe

https://issues.dlang.org/show_bug.cgi?id=18129 John Hall changed: What|Removed |Added CC|

[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 Keywords||rejects-valid, spec

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

https://issues.dlang.org/show_bug.cgi?id=18444 Carsten Blüggel changed: What|Removed |Added Depends on||18478 Referenced

[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 Blocks||18444 Referenced

[Issue 18621] core.sync.condition notify methods cannot be used from a (unix) signal handler

https://issues.dlang.org/show_bug.cgi?id=18621 James E. King III changed: What|Removed |Added Status|RESOLVED|CLOSED --

[Issue 18621] core.sync.condition notify methods cannot be used from a (unix) signal handler

https://issues.dlang.org/show_bug.cgi?id=18621 James E. King III changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 18621] core.sync.condition notify methods cannot be used from a (unix) signal handler

https://issues.dlang.org/show_bug.cgi?id=18621 --- Comment #1 from James E. King III --- Discussion on the forum, for reference: https://forum.dlang.org/thread/xakcezblunbflwxby...@forum.dlang.org --

[Issue 18621] New: core.sync.condition notify methods cannot be used from a (unix) signal handler

https://issues.dlang.org/show_bug.cgi?id=18621 Issue ID: 18621 Summary: core.sync.condition notify methods cannot be used from a (unix) signal handler Product: D Version: D2 Hardware: All OS: All

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

https://issues.dlang.org/show_bug.cgi?id=18620 RazvanN changed: What|Removed |Added CC|

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

https://issues.dlang.org/show_bug.cgi?id=18282 ag0aep6g changed: What|Removed |Added Status|RESOLVED|REOPENED

[Issue 15624] opApply with @safe and @system variants can't be used with foreach syntax

https://issues.dlang.org/show_bug.cgi?id=15624 --- Comment #1 from Walter Bright --- The foreach delegate is correctly constructed and its @safe-ty is correctly inferred. The overloading of opApply() is correct. The trouble is that the opApply() is selected by