[Issue 15857] incorrect checkimports mismatch for overload sets

https://issues.dlang.org/show_bug.cgi?id=15857 --- Comment #10 from Jacob Carlborg --- (In reply to Martin Nowak from comment #9) > (In reply to Jacob Carlborg from comment #8) > > This is not fixed in v2.071.1-b2. > > Are you sure? The merge is in v2.071.1-b1. I can give it

[Issue 15857] incorrect checkimports mismatch for overload sets

https://issues.dlang.org/show_bug.cgi?id=15857 --- Comment #11 from Jacob Carlborg --- (In reply to Martin Nowak from comment #9) > (In reply to Jacob Carlborg from comment #8) > > This is not fixed in v2.071.1-b2. > > Are you sure? The merge is in v2.071.1-b1. The issue persists

[Issue 16318] inherit from interface via abstract class

https://issues.dlang.org/show_bug.cgi?id=16318 --- Comment #2 from Lodovico Giaretta --- (In reply to b2.temp from comment #1) > Your request is not valid because it already works. You forget that an > interface method has to be implemented at least once before being >

[Issue 15371] __traits(getMember) should bypass the protection

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

[Issue 16115] [REG2.067] Wrong code with comma operator

https://issues.dlang.org/show_bug.cgi?id=16115 --- Comment #2 from Walter Bright --- https://github.com/dlang/dmd/pull/6054 --

[Issue 16318] inherit from interface via abstract class

https://issues.dlang.org/show_bug.cgi?id=16318 b2.t...@gmx.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 2525] Can't use `override` when implementing abstract base class's interface function

https://issues.dlang.org/show_bug.cgi?id=2525 b2.t...@gmx.com changed: What|Removed |Added CC||lodov...@giaretart.net --- Comment #11 from

[Issue 16318] inherit from interface via abstract class

https://issues.dlang.org/show_bug.cgi?id=16318 --- Comment #4 from Lodovico Giaretta --- (In reply to b2.temp from comment #3) > (In reply to Lodovico Giaretta from comment #2) > > If I inherit directly from an interface, I can override: > > > > == > >

[Issue 16380] New: no bindings for err.h

https://issues.dlang.org/show_bug.cgi?id=16380 Issue ID: 16380 Summary: no bindings for err.h Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: normal Priority: P1

[Issue 2525] Can't use `override` when implementing abstract base class's interface function

https://issues.dlang.org/show_bug.cgi?id=2525 --- Comment #12 from Lodovico Giaretta --- Any news on this? People periodically hits this issue and finds it very strange... --

[Issue 16381] Wrapping a float4 array leads to segfault.

https://issues.dlang.org/show_bug.cgi?id=16381 --- Comment #1 from Bartek Siudeja --- dmd: 2.068, 2.069 and 2.071 --

[Issue 16381] Wrapping a float4 array leads to segfault.

https://issues.dlang.org/show_bug.cgi?id=16381 Bartek Siudeja changed: What|Removed |Added Severity|enhancement |major --

[Issue 16381] New: Wrapping a float4 array leads to segfault.

https://issues.dlang.org/show_bug.cgi?id=16381 Issue ID: 16381 Summary: Wrapping a float4 array leads to segfault. Product: D Version: D2 Hardware: x86 OS: Mac OS X Status: NEW Severity: enhancement

[Issue 16381] Wrapping a float4 array leads to segfault.

https://issues.dlang.org/show_bug.cgi?id=16381 b2.t...@gmx.com changed: What|Removed |Added CC||b2.t...@gmx.com --- Comment #2 from

[Issue 16381] Wrapping a float4 array leads to segfault.

https://issues.dlang.org/show_bug.cgi?id=16381 ag0ae...@gmail.com changed: What|Removed |Added Keywords||ice CC|

[Issue 16381] Wrapping a float4 array leads to segfault.

https://issues.dlang.org/show_bug.cgi?id=16381 --- Comment #6 from b2.t...@gmx.com --- (In reply to Bartek Siudeja from comment #5) > does not help. So this seems about the return value of a function. Yes that's also what I said: return value == copy because float[4] doesn't fit in a CPU

[Issue 16381] Wrapping a float4 array leads to segfault.

https://issues.dlang.org/show_bug.cgi?id=16381 --- Comment #7 from b2.t...@gmx.com --- (In reply to b2.temp from comment #6) > (In reply to Bartek Siudeja from comment #5) > > does not help. So this seems about the return value of a function. > > Yes that's also what I said: return value == copy

[Issue 16318] inherit from interface via abstract class

https://issues.dlang.org/show_bug.cgi?id=16318 Steven Schveighoffer changed: What|Removed |Added CC|

[Issue 16381] Wrapping a float4 array leads to segfault.

https://issues.dlang.org/show_bug.cgi?id=16381 b2.t...@gmx.com changed: What|Removed |Added Hardware|x86 |All OS|Mac OS X

[Issue 16381] Wrapping a float4 array leads to segfault.

https://issues.dlang.org/show_bug.cgi?id=16381 --- Comment #3 from Bartek Siudeja --- True, but: My wrapper is a superclass of an abstract storage class, and not all implementations can return a reference to float4. Another superclass looks more or less like

[Issue 16381] Wrapping a float4 array leads to segfault.

https://issues.dlang.org/show_bug.cgi?id=16381 --- Comment #4 from b2.t...@gmx.com --- (In reply to Bartek Siudeja from comment #3) > True, but: > > My wrapper is a superclass of an abstract storage class, and not all > implementations can return a reference to float4. Another superclass looks

[Issue 16381] Wrapping a float4 array leads to segfault.

https://issues.dlang.org/show_bug.cgi?id=16381 --- Comment #5 from Bartek Siudeja --- If you do know a workaround I could use, I would be really grateful. Was checking some other options. Even changing opIndex into something like: float4 test(size_t idx) { float4 temp =

[Issue 16372] Broken links in documentation

https://issues.dlang.org/show_bug.cgi?id=16372 ag0ae...@gmail.com changed: What|Removed |Added Keywords||pull CC|

[Issue 14633] DDoc: false warnings for missing parameters on template declaration

https://issues.dlang.org/show_bug.cgi?id=14633 ag0ae...@gmail.com changed: What|Removed |Added CC||ag0ae...@gmail.com --- Comment #11 from