digitalmars.D.announce - DIP 1014--Hooking D's struct move semantics--Has Been Accepted
- Mike Parker (27/27) Nov 07 2018 I'm happy to announce that Walter and Andrei have rendered their
- test (3/12) Nov 07 2018 Thanks to all for the hard work.
- Per =?UTF-8?B?Tm9yZGzDtnc=?= (2/4) Nov 08 2018 Agreed!
- Jonathan M Davis (7/13) Nov 07 2018 I think that that probably sums the situation up pretty nicely. The fact
- 12345swordy (6/20) Nov 08 2018 This pull request is undoubtedly a major factor of Walter and
I'm happy to announce that Walter and Andrei have rendered their verdict on DIP 1014. They were in agreement on two points: they don't like it, but they know we need it. Given that there are no other alternative proposals and that they could see no alternative themselves, they decided to accept this DIP without modification. Thanks to Shachar Shemesh for pushing the DIP through to the end of the process and for his patience throughout. And congratulations on obtaining a successful result. I'll be getting the DIP queue moving again in short order. Walter and Andrei are currently considering DIP 1015 [2] and I expect to be able to announce their decision regarding it sooner than normal. I'll be launching the Final Review round for Manu's DIP 1016 [3] in the coming days. And given the approval of this DIP and a sense of urgency underlying the need to fix the flaws of postblit, the next DIP to move out of Draft Review will be Razvan's Copy Constructor proposal [4]. Immediately after that, I'll start pushing the older DIPs into Community Review back-to-back, without pause. [1] https://github.com/dlang/DIPs/blob/master/DIPs/accepted/DIP1014.md [2] https://github.com/dlang/DIPs/blob/8b7650bf491bf6c1c12e994ca7947f031b4480a6/DIPs/DIP1015.md [3] https://github.com/dlang/DIPs/blob/8b7650bf491bf6c1c12e994ca7947f031b4480a6/DIPs/DIP1016.md [4] https://github.com/dlang/DIPs/pull/129
Nov 07 2018
On Thursday, 8 November 2018 at 01:54:54 UTC, Mike Parker wrote:I'm happy to announce that Walter and Andrei have rendered their verdict on DIP 1014. They were in agreement on two points: they don't like it, but they know we need it. Given that there are no other alternative proposals and that they could see no alternative themselves, they decided to accept this DIP without modification. Thanks to Shachar Shemesh for pushing the DIP through to the end of the process and for his patience throughout. And congratulations on obtaining a successful result.Thanks to all for the hard work. Look forward DIP1016 to be approved.
Nov 07 2018
On Thursday, 8 November 2018 at 02:36:21 UTC, test wrote:Thanks to all for the hard work. Look forward DIP1016 to be approved.Agreed!
Nov 08 2018
On Wednesday, November 7, 2018 6:54:54 PM MST Mike Parker via Digitalmars-d- announce wrote:I'm happy to announce that Walter and Andrei have rendered their verdict on DIP 1014. They were in agreement on two points: they don't like it, but they know we need it. Given that there are no other alternative proposals and that they could see no alternative themselves, they decided to accept this DIP without modification.I think that that probably sums the situation up pretty nicely. The fact that we need something like this is just plain ugly, and if it starts getting used frequently, there's definitely a problem, but there are use cases, where it's going to be invaluable. - Jonathan M Davis
Nov 07 2018
On Thursday, 8 November 2018 at 03:04:06 UTC, Jonathan M Davis wrote:On Wednesday, November 7, 2018 6:54:54 PM MST Mike Parker via Digitalmars-d- announce wrote:This pull request is undoubtedly a major factor of Walter and Andrei approval of DIP 1014 https://github.com/dlang/druntime/pull/2310 AlexI'm happy to announce that Walter and Andrei have rendered their verdict on DIP 1014. They were in agreement on two points: they don't like it, but they know we need it. Given that there are no other alternative proposals and that they could see no alternative themselves, they decided to accept this DIP without modification.I think that that probably sums the situation up pretty nicely. The fact that we need something like this is just plain ugly, and if it starts getting used frequently, there's definitely a problem, but there are use cases, where it's going to be invaluable. - Jonathan M Davis
Nov 08 2018