[Issue 17448] Move semantics cause memory corruption and cryptic bugs

https://issues.dlang.org/show_bug.cgi?id=17448 --- Comment #12 from Walter Bright --- Interestingly, if you change: auto f() { return CallContext(18); } to: auto f() { CallContext c = CallContext(18); return c; } it will work, i.e. no moving is

[Issue 17448] Move semantics cause memory corruption and cryptic bugs

https://issues.dlang.org/show_bug.cgi?id=17448 --- Comment #11 from Walter Bright --- One possibility is to not allow escaping references to 'this' in @safe constructors. --

[Issue 17456] [REG2.075a] spurious lifetime diagnostic on delegates

https://issues.dlang.org/show_bug.cgi?id=17456 Vladimir Panteleev changed: What|Removed |Added CC|

[Issue 17453] I Have Many Issues

https://issues.dlang.org/show_bug.cgi?id=17453 --- Comment #6 from Soar --- and thank u reply for other problems. i will try do thats. --

[Issue 17453] I Have Many Issues

https://issues.dlang.org/show_bug.cgi?id=17453 --- Comment #5 from Soar --- (In reply to Rainer Schuetze from comment #4) > > when i create a project,has > > myproject/core/exception.d directory and file hierarchy > > > and im write a module in a file like "module winmain;" > >

[Issue 17456] [REG2.075a] spurious lifetime diagnostic on delegates

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

[Issue 17456] [REG2.075a] spurious lifetime diagnostic on delegates

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

[Issue 17448] Move semantics cause memory corruption and cryptic bugs

https://issues.dlang.org/show_bug.cgi?id=17448 --- Comment #10 from Andrei Alexandrescu --- (In reply to Shachar Shemesh from comment #9) > There are two issues here. The first is that @safe does not warn about > unsafe behavior. Affirmative. > Interesting, but unrelated to

[Issue 17453] I Have Many Issues

https://issues.dlang.org/show_bug.cgi?id=17453 --- Comment #4 from Rainer Schuetze --- > when i create a project,has > myproject/core/exception.d directory and file hierarchy > and im write a module in a file like "module winmain;" > but i cant use any other like "module

[Issue 17448] Move semantics cause memory corruption and cryptic bugs

https://issues.dlang.org/show_bug.cgi?id=17448 --- Comment #9 from Shachar Shemesh --- There are two issues here. The first is that @safe does not warn about unsafe behavior. Interesting, but unrelated to the Weka use case. The more interesting problem here is that certain

[Issue 17456] [REG2.075a] spurious lifetime diagnostic on delegates

https://issues.dlang.org/show_bug.cgi?id=17456 ag0ae...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 17456] [REG2.075a] spurious lifetime diagnostic on delegates

https://issues.dlang.org/show_bug.cgi?id=17456 --- Comment #1 from b2.t...@gmx.com --- (In reply to b2.temp from comment #0) > repro: > > > === > struct Foo > { > private void delegate() dg; > void assign() @safe {dg = } > void sameThis(){} > } > === > > yield: "address of variable

[Issue 8929] long.min is a Voldemort literal

https://issues.dlang.org/show_bug.cgi?id=8929 Zaydek changed: What|Removed |Added CC||zay...@icloud.com --- Comment #7

[Issue 17456] New: [REG2.075a] spurious lifetime diagnostic on delegates

https://issues.dlang.org/show_bug.cgi?id=17456 Issue ID: 17456 Summary: [REG2.075a] spurious lifetime diagnostic on delegates Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: regression

[Issue 17454] ABI non-conformity: produces unaligned placement of struct on stack

https://issues.dlang.org/show_bug.cgi?id=17454 ki...@gmx.net changed: What|Removed |Added CC||ki...@gmx.net --- Comment #6 from

[Issue 17448] Move semantics cause memory corruption and cryptic bugs

https://issues.dlang.org/show_bug.cgi?id=17448 Andrei Alexandrescu changed: What|Removed |Added CC||and...@erdani.com

[Issue 17455] New: [Functions] Incorrect description of "in" storage class.

https://issues.dlang.org/show_bug.cgi?id=17455 Issue ID: 17455 Summary: [Functions] Incorrect description of "in" storage class. Product: D Version: D2 Hardware: All URL: http://dlang.org/ OS:

[Issue 17454] ABI non-conformity: produces unaligned placement of struct on stack

https://issues.dlang.org/show_bug.cgi?id=17454 --- Comment #5 from Manu --- So, you're saying that MSVC is passing an output pointer as first arg? I'll try and confirm that. I didn't see that happening. --

[Issue 17454] ABI non-conformity: produces unaligned placement of struct on stack

https://issues.dlang.org/show_bug.cgi?id=17454 --- Comment #4 from Manu --- > What does happen is d_fun()'s caller allocates S, and then passes a pointer > to S to d_fun(), and d_fun() fills it in and returns that pointer to S. Interesting... so, what is __HID1 as

[Issue 17454] ABI non-conformity: produces unaligned placement of struct on stack

https://issues.dlang.org/show_bug.cgi?id=17454 Jacob Carlborg changed: What|Removed |Added CC||d...@me.com --- Comment #3

[Issue 17454] ABI non-conformity: produces unaligned placement of struct on stack

https://issues.dlang.org/show_bug.cgi?id=17454 --- Comment #2 from Walter Bright --- > d_fun returns a struct by value which appears by looking at the disassembly > that d_fun allocates room for the result value on it's stack, and then > returns a pointer to the

[Issue 17454] ABI non-conformity: produces unaligned placement of struct on stack

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