https://issues.dlang.org/show_bug.cgi?id=19584
Dlang Bot changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.dlang.org/show_bug.cgi?id=19945
Nathan S. changed:
What|Removed |Added
Keywords||betterC
--
https://issues.dlang.org/show_bug.cgi?id=19945
Issue ID: 19945
Summary: In betterC strange linker error can occur when
importing alias of template struct
Product: D
Version: D2
Hardware: All
OS: All
https://issues.dlang.org/show_bug.cgi?id=19916
--- Comment #23 from Manu ---
(In reply to Dennis from comment #22)
> (In reply to Manu from comment #18)
> > There is no world where access to
> > what can be confirmed to be uninitialised memory is @safe, period.
>
> This is just proof by assertio
https://issues.dlang.org/show_bug.cgi?id=19942
Dlang Bot changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.dlang.org/show_bug.cgi?id=19941
Dlang Bot changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.dlang.org/show_bug.cgi?id=19941
Dlang Bot changed:
What|Removed |Added
Keywords||pull
--- Comment #3 from Dlang Bot ---
@ibuclaw
https://issues.dlang.org/show_bug.cgi?id=5517
Basile-z changed:
What|Removed |Added
Status|REOPENED|RESOLVED
CC|
https://issues.dlang.org/show_bug.cgi?id=19584
Dlang Bot changed:
What|Removed |Added
Keywords||pull
--- Comment #4 from Dlang Bot ---
@Basile-
https://issues.dlang.org/show_bug.cgi?id=19616
--- Comment #1 from Bolpat ---
The same is true for interfaces:
interface I { }
interface A : I { }
bool condValue;
bool cond() { return condValue; }
pragma(msg, typeof(cond() ? &a : cond() ? &b : &i)); // I*
I* iPtr = cond() ? &a : &i; // fails wi
https://issues.dlang.org/show_bug.cgi?id=19943
--- Comment #3 from Basile-z ---
Okay I see. Maybe that outside this should behave like a cast, which then
behaves like you expect, i.e the field can be read but virtual dispatching is
not shortcut.
--
https://issues.dlang.org/show_bug.cgi?id=19941
--- Comment #2 from Iain Buclaw ---
Interestingly, it doesn't happen with const, enum or __gshared, only if the
declaration is marked immutable or shared does it trigger the bug.
--
https://issues.dlang.org/show_bug.cgi?id=19916
--- Comment #22 from Dennis ---
(In reply to Manu from comment #18)
> There is no world where access to
> what can be confirmed to be uninitialised memory is @safe, period.
This is just proof by assertion at this point.
(https://en.wikipedia.org/wik
https://issues.dlang.org/show_bug.cgi?id=19944
Issue ID: 19944
Summary: Some examples on std.file docs page raise
FileException
Product: D
Version: D2
Hardware: All
OS: All
Status: NEW
Se
https://issues.dlang.org/show_bug.cgi?id=19943
--- Comment #2 from FeepingCreature ---
To me, the problem isn't that you're able to do it from Own.C, the problem is
that you're able to do it from random.foo(), a function that is unrelated to
the A inheritance hierarchy.
--
https://issues.dlang.org/show_bug.cgi?id=19943
Basile-z changed:
What|Removed |Added
CC||b2.t...@gmx.com
Hardware|x86_64
https://issues.dlang.org/show_bug.cgi?id=18016
--- Comment #9 from Steven Schveighoffer ---
I'll start by saying, I think the operation is @safe, but I'm not sure it's
necessary for @safe code. You can indeed escape @safe with @trusted, so there
are likely ways around this. The easiest to prove r
https://issues.dlang.org/show_bug.cgi?id=8204
Simen Kjaeraas changed:
What|Removed |Added
CC||simen.kja...@gmail.com
--- Comment #3 from S
https://issues.dlang.org/show_bug.cgi?id=11061
Dlang Bot changed:
What|Removed |Added
Keywords||pull
--- Comment #2 from Dlang Bot ---
@Zevenbe
https://issues.dlang.org/show_bug.cgi?id=19891
Dlang Bot changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
20 matches
Mail list logo