[Dlang-internal] 15th Planning (national congress edition)

[Martin Nowak via Dlang-internal]

On Thursday, 10 November 2016 at 13:17:35 UTC, Dicebot wrote:
> This is my current main priority and I am aiming for 2.072.1 
> beta in 1 week, unless you have any objections. Currently 
> reducing and making bugzilla issues for all found regressions, 
> will give a go at fixing them after.

Yes, one week (let's say Nov 19-20th) sounds good for me as well.
I hope I can do the regression fix for 
https://trello.com/c/rWhNcvLt/246-issue-16574-reg-2-072-0-b1-unexplained-errors-about-functions-that-overridde-anything until then. Not sure about the others on the Trello heap.

> I'd also like to discuss enhancement for the proposal which 
> would remove the different between ref and pointer handling in 
> lifetime analysis and would allow to merge `return ref` and 
> `return scope` into one entity (at cost of loosing some 
> features that I consider of no practical use). This is not 
> necessary but would be nice to consider before design get set 
> in stone.

Yes it also seems to me we only need "return scope", "return 
scope ref", and "scope ref". Because "return ref" seems useless 
if you can escape the reference inside of the function.
Would like to have more than a gut feeling for that 
argument/decision.

> Ongoing problem in new D features is that last 20% of any 
> implementation gets forgotten in process of development and 
> when it released, it heavily lacks polish required to make good 
> impression.

You might want to try adding a scope card to the backlog that has 
a checklist for all the small stuff, though you'd need to have 
the examples as an attachment, gist, or so.

> (I don't have admin access to trello board btw, don't know if 
> it is
> intentional or accidental)

Done