On 05/01/2017 8:22 AM, Andrei Alexandrescu wrote:
> We release a brief Vision document summarizing the main goals we plan to
> pursue in the coming six months. This half we are focusing on three
> things: safety, lifetime management, and static introspection.
>
> https://wiki.dlang.org/Vision/2017H1
>
>
> Andrei

The suggestion I want to make related to druntime is, make TypeInfo/ModuleInfo actually have (opt-in) full reflection.
This can help decrease template bloat significantly for (de)serializers as well as making it so you don't have to explicitly tell your web router about all the routes (instead chuck a UDA down and be done with it!).

Andrei: we should talk in a few months about turning my (honors) dissertation into research papers. And maybe what I may end up doing for masters the following semester.

On Thursday, 5 January 2017 at 02:32:00 UTC, Chris Wright wrote:
>> Templatize dmd <-> druntime API
>
> I'm curious as to why. I'm guessing this is for things like creating runtime type information?

This thread (http://forum.dlang.org/post/mr7a65$2hc$1@digitalmars.com) should provide some context.

Mike

On Wednesday, 4 January 2017 at 19:22:33 UTC, Andrei Alexandrescu wrote:
> We release a brief Vision document summarizing the main goals we plan to pursue in the coming six months. This half we are focusing on three things: safety, lifetime management, and static introspection.
>
> https://wiki.dlang.org/Vision/2017H1
>
>
> Andrei

quote from the document:

> Redoing compiler code into lowerings and __traits-based introspection that leverage client code, thus moving compiler smarts into simpler library facilities

To simplify introspection with library traits that use the compiler "__traits()" someone has to remove the restrictions related to protection attributes. This is not a new topic. Without this, the new library traits won't work well and people won't use them.

On Wednesday, 4 January 2017 at 19:22:33 UTC, Andrei Alexandrescu wrote:
> We release a brief Vision document summarizing the main goals we plan to pursue in the coming six months. This half we are focusing on three things: safety, lifetime management, and static introspection.
>
> https://wiki.dlang.org/Vision/2017H1
>
>
> Andrei

Do we have a list of "high-impact research projects"?

On Thursday, January 05, 2017 04:43:12 Basile B. via Digitalmars-d-announce wrote:
> On Wednesday, 4 January 2017 at 19:22:33 UTC, Andrei Alexandrescu
>
> wrote:
> > We release a brief Vision document summarizing the main goals we plan to pursue in the coming six months. This half we are focusing on three things: safety, lifetime management, and static introspection.
> >
> > https://wiki.dlang.org/Vision/2017H1
> >
> >
> > Andrei
>
> quote from the document:
> > Redoing compiler code into lowerings and __traits-based introspection that leverage client code, thus moving compiler smarts into simpler library facilities
>
> To simplify introspection with library traits that use the compiler "__traits()" someone has to remove the restrictions related to protection attributes. This is not a new topic. Without this, the new library traits won't work well and people won't use them.

IIRC, it was already agreed that they had to be removed and would be soon, but we couldn't do it right away either because of code breakage or because it was a point release that was trying to get out the door. I'm thinking that it's supposed to be fixed in 2.073, but I'm not 100% sure..

- Jonathan M Davis

On Thursday, 5 January 2017 at 09:49:16 UTC, Jonathan M Davis wrote:
> On Thursday, January 05, 2017 04:43:12 Basile B. via Digitalmars-d-announce wrote:
>> On Wednesday, 4 January 2017 at 19:22:33 UTC, Andrei Alexandrescu
>>
>> wrote:
>> > We release a brief Vision document summarizing the main goals we plan to pursue in the coming six months. This half we are focusing on three things: safety, lifetime management, and static introspection.
>> >
>> > https://wiki.dlang.org/Vision/2017H1
>> >
>> >
>> > Andrei
>>
>> quote from the document:
>> > Redoing compiler code into lowerings and __traits-based introspection that leverage client code, thus moving compiler smarts into simpler library facilities
>>
>> To simplify introspection with library traits that use the compiler "__traits()" someone has to remove the restrictions related to protection attributes. This is not a new topic. Without this, the new library traits won't work well and people won't use them.
>
> IIRC, it was already agreed that they had to be removed and would be soon, but we couldn't do it right away either because of code breakage or because it was a point release that was trying to get out the door. I'm thinking that it's supposed to be fixed in 2.073, but I'm not 100% sure..
>
> - Jonathan M Davis

I don't known what did you decide in intern but when the discussion between users was hot (just after version 2.071.1 I think) I've proposed that: https://github.com/BBasile/DIPs/blob/3d5e3f81c541c6e23c69555a230b4d42a7bb6de6/DIPs/DIP8484.md

There's no need to DIP this, the idea is just to add an optional parameter that remove the compliance with the protection attributes. Anyway if this or any alternative is planned for the next version that's perfect.

On Wednesday, 4 January 2017 at 21:07:00 UTC, H. S. Teoh wrote:
> On Wed, Jan 04, 2017 at 08:45:09PM +0000, Stefan Koch via Digitalmars-d-announce wrote: [...]
>> I claim dips on templates. (as in the colloquial english for asserting
>> rights/ownership )
> [...]
>
> FYI, it's spelt "dibs" (with a 'b'). ;-)
>
>
> T

Actually, I think it's spelt "DIPs" (with capitalization) in dland ;)

-- Just a random thought

Am 05.01.2017 um 01:59 schrieb Paul O'Neil:
> On 01/04/2017 02:22 PM, Andrei Alexandrescu wrote:
>> We release a brief Vision document summarizing the main goals we plan to
>> pursue in the coming six months. This half we are focusing on three
>> things: safety, lifetime management, and static introspection.
>>
>> https://wiki.dlang.org/Vision/2017H1
>>
>>
>> Andrei
>
> What are the plans for the dub registry?  Have there been discussions
> already?

I'm not aware of concrete discussions w.r.t. the vision document, but the two major improvements that come to mind are GitHub authentication, which enables push notifications for repository changes, and some form of pagination for the package list views.

Also, one thing we discussed at the last DConf is a "popularity" score that would be used for sorting results. This would include things like download numbers and GitHub stars. It would also take into account the dependencies (which affects the download numbers), so that the score actually reflects the perceived popularity as close as possible.

Finally, we want to have a form of CI integration to put packages that have tests/pass tests first (i.e. give an incentive for package authors to setup and use CI for their project). Generating documentation is another possibility, as well as testing DMD frontend version compatibility.

On Wednesday, 4 January 2017 at 19:22:33 UTC, Andrei Alexandrescu wrote:
> We release a brief Vision document summarizing the main goals we plan to pursue in the coming six months. This half we are focusing on three things: safety, lifetime management, and static introspection.
>
> https://wiki.dlang.org/Vision/2017H1
>
>
> Andrei

dub registry required review
1. By myself current page rename to "last updates", and "Main" may be (scoped) category view?
IMHO main page currently unfriendly

2. dub registry search unexpected
i'm looking for network libs, entered "net" and take:
...
freeimage
dyaml
...
???
Than query for "network", very different result

P/S
strange search one of cases why registry has a lot of similar projects