[Issue 3345] Static and nonstatic methods with the same name should be allowed

https://issues.dlang.org/show_bug.cgi?id=3345 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #20 from Dlang Bot --- @WalterB

[Issue 16218] Windows std.file.readImpl should be marked @system

https://issues.dlang.org/show_bug.cgi?id=16218 Vlăduț Chicoș changed: What|Removed |Added CC||vladut.chi...@gmail.com Assignee|n

[Issue 22162] New: conv.to doesn't handle strings to user defined arrays

https://issues.dlang.org/show_bug.cgi?id=22162 Issue ID: 22162 Summary: conv.to doesn't handle strings to user defined arrays Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: enhanceme

[Issue 22119] [Functions] Function Overloading clarity for int[] and strings

https://issues.dlang.org/show_bug.cgi?id=22119 --- Comment #2 from crazymonk...@gmail.com --- (In reply to mhh from comment #1) > Is this not implied by the existing overload matching rules? You were part of the conversation on discord and didnt see it either? its implied if I understand the rule

[Issue 15828] DMD should refuse comparing unions

https://issues.dlang.org/show_bug.cgi?id=15828 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #4 from Dlang Bot --- @teodutu

[Issue 16339] insertInPlace should be tested for unions and classes

https://issues.dlang.org/show_bug.cgi?id=16339 Dlang Bot changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 16339] insertInPlace should be tested for unions and classes

https://issues.dlang.org/show_bug.cgi?id=16339 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #3 from Dlang Bot --- @lucica2

[Issue 22161] importC: Support parsing C asm expressions

https://issues.dlang.org/show_bug.cgi?id=22161 Iain Buclaw changed: What|Removed |Added Keywords||ImportC, rejects-valid CC|

[Issue 22161] New: importC: Support parsing C asm expressions

https://issues.dlang.org/show_bug.cgi?id=22161 Issue ID: 22161 Summary: importC: Support parsing C asm expressions Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: major Priority:

[Issue 22160] importC: Error: redeclaring `module test` as `struct test`

https://issues.dlang.org/show_bug.cgi?id=22160 Iain Buclaw changed: What|Removed |Added Keywords||ImportC, rejects-valid CC|

[Issue 22160] New: importC: Error: redeclaring `module test` as `struct test`

https://issues.dlang.org/show_bug.cgi?id=22160 Issue ID: 22160 Summary: importC: Error: redeclaring `module test` as `struct test` Product: D Version: D2 Hardware: All OS: All Status: NEW

[Issue 22159] "==" causeses error for array of classes in safe method

https://issues.dlang.org/show_bug.cgi?id=22159 RazvanN changed: What|Removed |Added Component|dmd |druntime --- Comment #2 from RazvanN --- It turns

[Issue 22159] "==" causeses error for array of classes in safe method

https://issues.dlang.org/show_bug.cgi?id=22159 RazvanN changed: What|Removed |Added Severity|normal |regression --- Comment #1 from RazvanN --- Looks

[Issue 22159] "==" causeses error for array of classes in safe method

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

[Issue 19919] Incorrect initialization of union when first member isn't marked = void

https://issues.dlang.org/show_bug.cgi?id=19919 --- Comment #6 from Dlang Bot --- dlang/dmd pull request #12899 "End deprecation period for incorrect initialization of union when first member isn't marked (Issues 19919 and 19917)" was merged into master: - 5600f50c129c45d7867238a0488fc49f8aa167cd

[Issue 19917] unions should require that all members are `= void` initialised

https://issues.dlang.org/show_bug.cgi?id=19917 --- Comment #12 from Dlang Bot --- dlang/dmd pull request #12899 "End deprecation period for incorrect initialization of union when first member isn't marked (Issues 19919 and 19917)" was merged into master: - 5600f50c129c45d7867238a0488fc49f8aa167c

[Issue 22159] New: "==" causeses error for array of classes in safe method

https://issues.dlang.org/show_bug.cgi?id=22159 Issue ID: 22159 Summary: "==" causeses error for array of classes in safe method Product: D Version: D2 Hardware: All OS: All Status: NEW Se

[Issue 3345] Static and nonstatic methods with the same name should be allowed

https://issues.dlang.org/show_bug.cgi?id=3345 Walter Bright changed: What|Removed |Added Keywords||spec Component|dmd

[Issue 3345] Static and nonstatic methods with the same name should be allowed

https://issues.dlang.org/show_bug.cgi?id=3345 --- Comment #19 from Walter Bright --- Not yet, because the spec neglects to mention this behavior. I'll see about fixing that tomorrow. https://dlang.org/spec/function.html#function-overloading --

[Issue 3345] Static and nonstatic methods with the same name should be allowed

https://issues.dlang.org/show_bug.cgi?id=3345 --- Comment #18 from RazvanN --- Do you suggest we close this as invalid? --

[Issue 3345] Static and nonstatic methods with the same name should be allowed

https://issues.dlang.org/show_bug.cgi?id=3345 --- Comment #17 from Walter Bright --- > But having different error messages depending on the order of declarations is > definitely wrong. Probably, but it's a minor issue, as both messages are correct. --

[Issue 3345] Static and nonstatic methods with the same name should be allowed

https://issues.dlang.org/show_bug.cgi?id=3345 --- Comment #16 from RazvanN --- (In reply to Walter Bright from comment #15) > > Otherwise there is no way to explain how .classinfo works in terms of D > > facilities. > > It is explained by if the member function is static, the 'this' reference i

[Issue 22158] Optimize away empty loops that have no side effect

https://issues.dlang.org/show_bug.cgi?id=22158 Vladimir Panteleev changed: What|Removed |Added Summary|Optimize away empty loops |Optimize away empty loops

[Issue 22158] Optimize away empty loops

https://issues.dlang.org/show_bug.cgi?id=22158 --- Comment #1 from Basile-z --- I suggest to edit the tittle: Optimize away empty loops -> Optimize away empty loops that have no side effect because the Test and the Increment can do things even if the loop body is empty --

[Issue 3345] Static and nonstatic methods with the same name should be allowed

https://issues.dlang.org/show_bug.cgi?id=3345 Walter Bright changed: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment #15 from

[Issue 22158] Optimize away empty loops

https://issues.dlang.org/show_bug.cgi?id=22158 moonlightsenti...@disroot.org changed: What|Removed |Added Keywords||backend CC|

[Issue 3345] Static and nonstatic methods with the same name should be allowed

https://issues.dlang.org/show_bug.cgi?id=3345 --- Comment #14 from Max Samukha --- (In reply to Richard Cattermole from comment #13) > Add @safe to your main function. > > onlineapp.d(11): Error: `this` reference necessary to take address of member > `foo` in `@safe` function `main` > onlineapp.

[Issue 22158] New: Optimize away empty loops

https://issues.dlang.org/show_bug.cgi?id=22158 Issue ID: 22158 Summary: Optimize away empty loops Product: D Version: D2 Hardware: x86_64 OS: All Status: NEW Keywords: performance Severity: enhance