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

https://issues.dlang.org/show_bug.cgi?id=18110 Issue 18110 depends on issue 18444, which changed state. Issue 18444 Summary: [DIP25][DIP1000] Tracking issue for: "The implementation doesn't match DIPs 25/1000" https://issues.dlang.org/show_bug.cgi?id=18444 What|Removed

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

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

[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 Walter Bright changed: What|Removed |Added CC|

[Issue 18553] Inline assembler: CR2, CR3 control registers not available in 64-bit code

https://issues.dlang.org/show_bug.cgi?id=18553 bitter.ta...@gmx.com changed: What|Removed |Added CC||bitter.ta...@gmx.com --- Comment #1

[Issue 18627] std.complex is a lot slower than builtin complex types at number crunching

https://issues.dlang.org/show_bug.cgi?id=18627 Iain Buclaw changed: What|Removed |Added CC||ibuc...@gdcproject.org

[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 --- Comment #4 from jpdut...@gmail.com --- (In reply to Walter Bright from comment #2) > The error is on the function returning the reference, not the function using > (or not using) the return value. Because of separate compilation, it has to > be

[Issue 18295] [Scope][dip1000] `scope class` check too conservative under -dip1000

https://issues.dlang.org/show_bug.cgi?id=18295 --- Comment #2 from Walter Bright --- I propose abandoning `scope class C { ... }` altogether. See https://github.com/dlang/dlang.org/pull/2027 --

[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 --- Comment #2 from Walter Bright --- (In reply to jpdutoit from comment #0) > In the code below, since fn2 is not returning by reference, it should not > matter that fn1_normal and fn1_template is returning by reference.

[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 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED

[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 18478, which changed state. Issue 18478 Summary: 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 What

[Issue 18598] cyclic constructor calls have undefined behavior but are accepted in @safe code

https://issues.dlang.org/show_bug.cgi?id=18598 Walter Bright changed: What|Removed |Added CC|

[Issue 18637] New: [scope][DIP1000] "Error: returning & i escapes a reference to local variable i" where it's inappropriate

https://issues.dlang.org/show_bug.cgi?id=18637 Issue ID: 18637 Summary: [scope][DIP1000] "Error: returning & i escapes a reference to local variable i" where it's inappropriate Product: D Version: D2

[Issue 18631] std.random.choice does not work with const arrays

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

[Issue 18598] cyclic constructor calls have undefined behavior but are accepted in @safe code

https://issues.dlang.org/show_bug.cgi?id=18598 --- Comment #2 from ag0aep6g --- (In reply to Walter Bright from comment #1) > I don't know a way to assign defined behavior to overflowing the stack :-( Is that a problem for normal (non-constructor) functions as well?

[Issue 18627] std.complex is a lot slower than builtin complex types at number crunching

https://issues.dlang.org/show_bug.cgi?id=18627 --- Comment #5 from ponce --- Division with DMD 32-bit: With cfloat: 1 minute, 18 secs, 451 ms, 932 ╬╝s, and 9 hnsecs With cdouble: 1 minute, 19 secs, 747 ms, 70 ╬╝s, and 5 hnsecs With Complex!float: 27 secs, 412 ms, 926 ╬╝s, and

[Issue 18631] std.random.choice does not work with const arrays

https://issues.dlang.org/show_bug.cgi?id=18631 --- Comment #1 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/403141166b624c47cafcb5904724b62271f63785 fix issue 18631 - Allow choice to work with const

[Issue 18627] std.complex is a lot slower than builtin complex types at number crunching

https://issues.dlang.org/show_bug.cgi?id=18627 --- Comment #4 from ponce --- This benchmark is a variation that does only division. --- divide.d import std.string; import std.datetime; import std.datetime.stopwatch : benchmark, StopWatch; import std.complex; import

[Issue 18637] [scope][DIP1000] "Error: returning & i escapes a reference to local variable i" where it's inappropriate

https://issues.dlang.org/show_bug.cgi?id=18637 --- Comment #1 from Carsten Blüggel --- For reference: https://github.com/dlang/phobos/blob/master/dip1000.mak --

[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 --- Comment #5 from Carsten Blüggel --- (In reply to Walter Bright from comment #3) > (In reply to Carsten Blüggel from comment #1) > > Another error example from phobos that appeared in master within the last > > ~24h: > > I

[Issue 18534] Wrong code for ?: operator when compiling with -O

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

[Issue 17770] Null pointer access in CTFE code

https://issues.dlang.org/show_bug.cgi?id=17770 bitter.ta...@gmx.com changed: What|Removed |Added CC||bitter.ta...@gmx.com --- Comment #2

[Issue 18534] Wrong code for ?: operator when compiling with -O

https://issues.dlang.org/show_bug.cgi?id=18534 --- Comment #4 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/f9ed34003d9b0f533a37850540b02929586e7a76 fix Issue 18534 - Wrong code for ?: operator when compiling

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

https://issues.dlang.org/show_bug.cgi?id=18444 --- Comment #3 from Carsten Blüggel --- (In reply to Walter Bright from comment #2) > Is there any reason not to close this? The `safe` keyword does the job to > connect these related issues. Thank You so much for working hard on

[Issue 18604] in parameter storage class should be deprecated

https://issues.dlang.org/show_bug.cgi?id=18604 --- Comment #5 from anonymous4 --- If one wants to remove `in` attribute the fix is rather simple 's/in/const/' --

[Issue 16037] assigning delegate to a scope variable shouldn't allocate closure

https://issues.dlang.org/show_bug.cgi?id=16037 --- Comment #7 from anonymous4 --- Clarify how breaking invalid code is gratuitous. If the code is correct it won't be broken. --

[Issue 18627] std.complex is a lot slower than builtin complex types at number crunching

https://issues.dlang.org/show_bug.cgi?id=18627 --- Comment #6 from ponce --- Conversely complex divide seems faster with DMD with std.complex than builtins. --

[Issue 18627] std.complex is a lot slower than builtin complex types at number crunching

https://issues.dlang.org/show_bug.cgi?id=18627 Seb changed: What|Removed |Added CC||greensunn...@gmail.com ---

[Issue 18638] New: The main override of std.range.zip could infer @nogc and nothrow

https://issues.dlang.org/show_bug.cgi?id=18638 Issue ID: 18638 Summary: The main override of std.range.zip could infer @nogc and nothrow Product: D Version: D2 Hardware: All OS: All Status: NEW

[Issue 18638] The main override of std.range.zip could infer @nogc and nothrow

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

[Issue 18604] in parameter storage class should be deprecated

https://issues.dlang.org/show_bug.cgi?id=18604 --- Comment #3 from anonymous4 --- (In reply to Seb from comment #0) > `in` currently just means `const` That antifeature was only sort of done for safe code, whatever you do, system code shouldn't be affected. Though given

[Issue 18604] in parameter storage class should be deprecated

https://issues.dlang.org/show_bug.cgi?id=18604 --- Comment #4 from anonymous4 --- Also the reason why safe code receives breakage is because it's invalid, and there should be no guarantee for invalid code to work. --

[Issue 16519] toHexString always returns stack allocated string

https://issues.dlang.org/show_bug.cgi?id=16519 --- Comment #4 from anonymous4 --- (In reply to Seb from comment #3) > foo.d(8): Deprecation: slice of static array temporary returned by > toHexString(hash) assigned to longer lived variable a > > but I still think we

[Issue 16037] assigning delegate to a scope variable shouldn't allocate closure

https://issues.dlang.org/show_bug.cgi?id=16037 --- Comment #8 from anonymous4 --- Anyway, if `in` loses scope semantics, it will break @nogc code like in the example above, you can't eliminate breakage completely here. --

[Issue 16037] assigning delegate to a scope variable shouldn't allocate closure

https://issues.dlang.org/show_bug.cgi?id=16037 --- Comment #9 from Mathias Lang --- @anonymous4: For starter, DIP1000 fixes only apply to @safe function ATM. While it's a decision I don't agree with personally, it's the path that was chosen and changing it would

[Issue 18639] New: VisualD - First 5 minutes - Improve list of project wizards, propritise MSBuild projects

https://issues.dlang.org/show_bug.cgi?id=18639 Issue ID: 18639 Summary: VisualD - First 5 minutes - Improve list of project wizards, propritise MSBuild projects Product: D Version: D2 Hardware: x86 OS:

[Issue 18640] New: VisualD - First 5 minutes - Default debuginfo configuration emits warnings.

https://issues.dlang.org/show_bug.cgi?id=18640 Issue ID: 18640 Summary: VisualD - First 5 minutes - Default debuginfo configuration emits warnings. Product: D Version: D2 Hardware: All OS: Windows

[Issue 18641] New: VisualD - First 5 minutes - Improve experience adding .d files to existing C++ projects

https://issues.dlang.org/show_bug.cgi?id=18641 Issue ID: 18641 Summary: VisualD - First 5 minutes - Improve experience adding .d files to existing C++ projects Product: D Version: D2 Hardware: x86 OS: Windows

[Issue 18628] @disable this(this) erroneously adds `__postblit` member

https://issues.dlang.org/show_bug.cgi?id=18628 --- Comment #5 from johanenge...@weka.io --- (In reply to RazvanN from comment #1) > Well, the struct defines the member, it's just that it is disabled. One > might argue that the output is correct and the programmer needs to check if > the member is

[Issue 18627] std.complex is a lot slower than builtin complex types at number crunching

https://issues.dlang.org/show_bug.cgi?id=18627 --- Comment #8 from ponce --- @Seb: It's not only about DMD, there is a 2x performance regression with Complex!double vs cdouble using LDC. There are probably more I haven't exposed yet. And yes, I use cdouble for designing IIR

[Issue 16662] Can't call std.variant.visit from a pure function

https://issues.dlang.org/show_bug.cgi?id=16662 --- Comment #3 from Paul Backus --- I've made some progress on this, but am unable to make VariantN.peek pure, because this if statement if (type != typeid(T)) return null; ...calls object.opEquals, which is

[Issue 18628] @disable this(this) erroneously adds `__postblit` member

https://issues.dlang.org/show_bug.cgi?id=18628 --- Comment #6 from johanenge...@weka.io --- (In reply to johanengelen from comment #5) > > Currently, adding `@disable this(this)` to a struct that normally wouldn't > have a postblit, actually makes the compiler emit a postblit function

[Issue 18637] [scope][DIP1000] "copying & i into allocated memory escapes a reference to local variable i" where it's inappropriate

https://issues.dlang.org/show_bug.cgi?id=18637 Carsten Blüggel changed: What|Removed |Added Summary|[scope][DIP1000] "Error:|[scope][DIP1000]

[Issue 17784] [scope][DIP1000] Confusing error message for escaping local via new-expression

https://issues.dlang.org/show_bug.cgi?id=17784 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/940cfd79fa681809e0e983faa1576d2efebf0953 fix Issue 17784 - [scope][DIP1000] Confusing error message

[Issue 18607] using labelled continue in tuple foreach can break pure and @safe

https://issues.dlang.org/show_bug.cgi?id=18607 Walter Bright changed: What|Removed |Added CC|

[Issue 18642] New: VisualD - Demangle link errors?

https://issues.dlang.org/show_bug.cgi?id=18642 Issue ID: 18642 Summary: VisualD - Demangle link errors? Product: D Version: D2 Hardware: x86 OS: Windows Status: NEW Severity: enhancement Priority:

[Issue 17784] [scope][DIP1000] Confusing error message for escaping local via new-expression

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

[Issue 17331] appender can't be used for initialization twice

https://issues.dlang.org/show_bug.cgi?id=17331 Tomáš Chaloupka changed: What|Removed |Added CC||chalu...@gmail.com

[Issue 17331] appender can't be used for initialization twice

https://issues.dlang.org/show_bug.cgi?id=17331 --- Comment #2 from Tomáš Chaloupka --- My guess is that problem is here: https://github.com/dlang/phobos/blob/master/std/array.d#L2884 As this constructor is called when appender is used with null arr parameter. So I guess that

[Issue 18604] in parameter storage class should be deprecated

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

[Issue 18603] Illegal instruction: 4 on Mac OS 10.7.5 Leopard

https://issues.dlang.org/show_bug.cgi?id=18603 --- Comment #5 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dlang.org https://github.com/dlang/dlang.org/commit/4e40131b9f176fc6de0cd58261726e0c33c5ecce Fix Issue 18603 - Update minimally required

[Issue 18603] Illegal instruction: 4 on Mac OS 10.7.5 Leopard

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