https://github.com/dlang/DIPs/blob/44b0d4ec0da6a2e797ede748fb1e81cd6db10371/DIPs/DIP1030.md

I believe it's possible to strike a balance between binary compatibility
between upgrades, source compatibility for .di files, and programmer
convenience. Why doesn't that DIP have its own Pull Request on GitHub?

On Wednesday, 10 June 2020 at 18:36:14 UTC, James Lu wrote:
> https://github.com/dlang/DIPs/blob/44b0d4ec0da6a2e797ede748fb1e81cd6db10371/DIPs/DIP1030.md
>
> I believe it's possible to strike a balance between binary compatibility
> between upgrades, source compatibility for .di files, and programmer
> convenience. Why doesn't that DIP have its own Pull Request on GitHub?

Patience, it need to be approved before the pr request be made. The lots of the discussion being made regarding the dip.

-Alex

On Wednesday, 10 June 2020 at 18:58:44 UTC, 12345swordy wrote:
> Patience, it need to be approved before the pr request be made. The lots of the discussion being made regarding the dip.
>
> -Alex

Where is a link to such discussion?

On 6/12/20 8:04 AM, James Lu wrote:
> On Wednesday, 10 June 2020 at 18:58:44 UTC, 12345swordy wrote:
>> Patience, it need to be approved before the pr request be made. The lots of the discussion being made regarding the dip.
>>
> 
> Where is a link to such discussion?

It should be in the DIP I would think, but it appears not to be. It says that the DIP is in community review round 1. Mike?

-Steve

On Friday, 12 June 2020 at 12:31:10 UTC, Steven Schveighoffer wrote:
> On 6/12/20 8:04 AM, James Lu wrote:
>> On Wednesday, 10 June 2020 at 18:58:44 UTC, 12345swordy wrote:
>>> Patience, it need to be approved before the pr request be made. The lots of the discussion being made regarding the dip.
>>>
>> 
>> Where is a link to such discussion?
>
> It should be in the DIP I would think, but it appears not to be. It says that the DIP is in community review round 1. Mike?
>
> -Steve

The link in this thread is to the revision that was under Community Review, not the one in master. It's already gone through Final Review. Although, I just realized I forgot to update it once the Final Review ended. That's done now. The current revision:

https://github.com/dlang/DIPs/blob/master/DIPs/DIP1030.md

On Friday, 12 June 2020 at 12:33:45 UTC, Mike Parker wrote:
> On Friday, 12 June 2020 at 12:31:10 UTC, Steven Schveighoffer
>
> The link in this thread is to the revision that was under Community Review, not the one in master. It's already gone through Final Review. Although, I just realized I forgot to update it once the Final Review ended. That's done now. The current revision:
>
> https://github.com/dlang/DIPs/blob/master/DIPs/DIP1030.md

So is it now accepted?

On Wednesday, 24 June 2020 at 14:29:04 UTC, sighoya wrote:

> So is it now accepted?

No. It's in the queue for Formal Assessment.

On Wednesday, 24 June 2020 at 14:39:39 UTC, Mike Parker wrote:
> On Wednesday, 24 June 2020 at 14:29:04 UTC, sighoya wrote:
>
>> So is it now accepted?
>
> No. It's in the queue for Formal Assessment.

Thanks for clarification. And what is the state of the formal Assessment, where is it logged?

On Thursday, 25 June 2020 at 18:47:05 UTC, sighoya wrote:

>
> Thanks for clarification. And what is the state of the formal Assessment, where is it logged?

I don't know what you mean. As a general rule, there is only one DIP in Formal Assessment at a time. You can see the status of all DIPs under review here:

https://github.com/dlang/DIPs/blob/master/DIPs/README.md

Currently, DIP 1029 is in Formal Assessment. I actually expect to make an announcement on its disposition before Saturday. I'll move 1030 into Formal Assessment sometime thereafter, though it won't be immediately. There was a controversy over the DIP 1028 decision last month:

https://forum.dlang.org/post/rwjxbgsauknjjrvousti@forum.dlang.org

TL:DR, should a language maintainer be evaluating his own DIP? Because of that, we've slowed things down a bit. I won't move 1030 forward until we resolve that question, but I expect that to happen very soon.