On Friday, 11 July 2014 at 22:03:37 UTC, H. S. Teoh via Digitalmars-d wrote:
> Maybe what we should do, is to have everyone post their current
> (probably incomplete) drafts of what scope should do, so that we have
> everything on the table and we can talk about what should be kept, what
> should be discarded, etc.. It may be, that the best design is not what
> any one of us has right now, but some combination of multiple current
> proposals.

I've just done so for mine:
http://wiki.dlang.org/User:Schuetzm/scope

On 7/13/2014 3:47 AM, Dicebot wrote:
> On Sunday, 13 July 2014 at 07:18:53 UTC, Walter Bright wrote:
>> On 7/10/2014 5:54 AM, Dicebot wrote:
>>> No one but Walter / Andrei can do anything about it. Right now we are in weird
>>> situation when they call for "lieutenants" but are not ready to abandon decision
>>> power. It can't possibly work that way. No amount of volunteer effort will help
>>> when so many PR stall waiting for resolution comment from one of language
>>> "generals".
>>
>> Here are the teams with Pulling Power:
>>
>>   https://github.com/orgs/D-Programming-Language/teams
>>
>> Team Phobos, for example, has 25 members. Including you!
>
> You do realize that Andrei has added me to that list exactly after this message
> I have posted to shut me up? :grumpy:

No, I didn't realize that, thanks for letting me know. But there are still 24 other members, which is a lot more than just Andrei and I.

On 7/13/2014 4:05 AM, Dicebot wrote:
> Also I was not speaking originally about "all good" pull requests just waiting
> to be merged but about stuff that hits some controversial language/Phobos parts
> and requires some decision if it can be accepted at all. Pretty much no one but
> you can make such judgement even if there are many people with merge rights.
>
> It is probably more of an issue for DMD than Phobos because almost any
> enhancement for language needs to get your approval or go away.

That is true, but Andrei and I also rely heavily on feedback from you guys about those issues. For example, Sean's std.concurrency pull. I gotta rely on reviews from you fellows, because I am hardly an expert on best practices for concurrency programming. In fact I'm rather a newbie at it.

On Sun, Jul 13, 2014 at 02:58:27PM +0000, via Digitalmars-d wrote:
> On Friday, 11 July 2014 at 22:03:37 UTC, H. S. Teoh via Digitalmars-d wrote:
> >Maybe what we should do, is to have everyone post their current (probably incomplete) drafts of what scope should do, so that we have everything on the table and we can talk about what should be kept, what should be discarded, etc.. It may be, that the best design is not what any one of us has right now, but some combination of multiple current proposals.
> 
> I've just done so for mine: http://wiki.dlang.org/User:Schuetzm/scope

Mine is here:

	http://wiki.dlang.org/User:Quickfur/DIP_scope


T

-- 
Turning your clock 15 minutes ahead won't cure lateness---you're just making time go faster!

On Sunday, 13 July 2014 at 18:20:12 UTC, Walter Bright wrote:
> On 7/13/2014 4:05 AM, Dicebot wrote:
>> Also I was not speaking originally about "all good" pull requests just waiting
>> to be merged but about stuff that hits some controversial language/Phobos parts
>> and requires some decision if it can be accepted at all. Pretty much no one but
>> you can make such judgement even if there are many people with merge rights.
>>
>> It is probably more of an issue for DMD than Phobos because almost any
>> enhancement for language needs to get your approval or go away.
>
> That is true, but Andrei and I also rely heavily on feedback from you guys about those issues. For example, Sean's std.concurrency pull. I gotta rely on reviews from you fellows, because I am hardly an expert on best practices for concurrency programming. In fact I'm rather a newbie at it.

I will keep an eye std.concurrency but I what should I do to convince you say a word or two about DMD PR that makes some language change? :)

On 7/14/2014 9:56 AM, Dicebot wrote:
> I will keep an eye std.concurrency but I what should I do to convince you say a
> word or two about DMD PR that makes some language change? :)

I still believe that Andrei & I need to approve language change PRs. These can be very disruptive and not easily reverted if they aren't right. That said, we still strongly rely on feedback on these from the community.

For example,

  https://issues.dlang.org/show_bug.cgi?id=11946

On Monday, 14 July 2014 at 18:30:34 UTC, Walter Bright wrote:
> On 7/14/2014 9:56 AM, Dicebot wrote:
>> I will keep an eye std.concurrency but I what should I do to convince you say a
>> word or two about DMD PR that makes some language change? :)
>
> I still believe that Andrei & I need to approve language change PRs. These can be very disruptive and not easily reverted if they aren't right. That said, we still strongly rely on feedback on these from the community.
>
> For example,
>
>   https://issues.dlang.org/show_bug.cgi?id=11946

I mean something like this : https://github.com/D-Programming-Language/dmd/pull/3651 - change that was implemented, generally approved in NG discussion, adjusted to all review comments etc but still doesn't not have even single comment from you or Andrei if it is even has chance for being accepted. Just a short "Thinking, not sure" is much less discouraging than no comments at all.

On 7/14/14, 12:10 PM, Dicebot wrote:
> On Monday, 14 July 2014 at 18:30:34 UTC, Walter Bright wrote:
>> On 7/14/2014 9:56 AM, Dicebot wrote:
>>> I will keep an eye std.concurrency but I what should I do to convince
>>> you say a
>>> word or two about DMD PR that makes some language change? :)
>>
>> I still believe that Andrei & I need to approve language change PRs.
>> These can be very disruptive and not easily reverted if they aren't
>> right. That said, we still strongly rely on feedback on these from the
>> community.
>>
>> For example,
>>
>>   https://issues.dlang.org/show_bug.cgi?id=11946
>
> I mean something like this :
> https://github.com/D-Programming-Language/dmd/pull/3651 - change that
> was implemented, generally approved in NG discussion, adjusted to all
> review comments etc but still doesn't not have even single comment from
> you or Andrei if it is even has chance for being accepted. Just a short
> "Thinking, not sure" is much less discouraging than no comments at all.

Good example. Let me look into it! -- Andrei

On 7/14/2014 12:10 PM, Dicebot wrote:
> On Monday, 14 July 2014 at 18:30:34 UTC, Walter Bright wrote:
>> For example,
>>
>>   https://issues.dlang.org/show_bug.cgi?id=11946
>
> I mean something like this :
> https://github.com/D-Programming-Language/dmd/pull/3651 - change that was
> implemented, generally approved in NG discussion, adjusted to all review
> comments etc but still doesn't not have even single comment from you or Andrei
> if it is even has chance for being accepted. Just a short "Thinking, not sure"
> is much less discouraging than no comments at all.

At the moment my focus is to get 2.066 out. If I don't, it'll just drift on and never happen. 11946 is one of the problem areas.

On 14/07/14 18:16, H. S. Teoh via Digitalmars-d wrote:

> Mine is here:
>
> 	http://wiki.dlang.org/User:Quickfur/DIP_scope

From the DIP:

"The 'scope' keyword has been around for years, yet it is barely implemented and it's unclear just what it's supposed to mean"

I don't know if it's worth clarify but "scope" currently has various features.

1. Allocate classes on the stack: "scope bar = new Bar()"
2. Forcing classes to be allocated on the stack: "scope class Bar {}"
3. The scope-statement: "scope(exit) file.close()"
4. Scope parameters. This is the part that is unclear what is means/is supposed to mean in the current language

-- 
/Jacob Carlborg