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

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

Nice, a list of concrete tasks, well done.

Only one criticism, some are too short: took me a bit to understand what "High-level shared library wrapper" meant, a better way to create and deal with shared libraries?  If so, only reason I got that is because of your recent forum posts asking about loading shared libraries.  Not sure what you want overhauled about the dub registry either, might want to expand on those, so someone interested could pick up on 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

I claim dips on templates. (as in the colloquial english for asserting rights/ownership )
I can't wait to improve that situation.

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

-- 
It won't be covered in the book. The source code has to be useful for something, after all. -- Larry Wall

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

I like the social media part. More people, more man power, more noise about D.

On Wednesday, 4 January 2017 at 21:21:17 UTC, aberba wrote:
>
> I like the social media part. More people, more man power, more noise about D.

I would read it as, with better signal-to-noise ratio.

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?

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
>

Hi, its interesting to view this in context of previous vision documents:

https://wiki.dlang.org/Vision/2015H1
https://wiki.dlang.org/Vision/2015H2
https://wiki.dlang.org/Vision/2016H1
https://wiki.dlang.org/Vision/2016H2

It seems safety and memory management have appeared in all of the documents, so presumably the goals haven't been achieved yet. I think it would be helpful to have more explicit definition of what it would mean for these features to be "done" and is that the aim for H1 2017.

C++ integration has disappeared? Is this now "done"?

> Templatize dmd <-> druntime API

I'm curious as to why. I'm guessing this is for things like creating runtime type information?

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

There's a lot of benefits to it: it'd simplify the compiler a bit, it'd simplify making custom runtimes, and it'd give us options to both expand and minimize the runtime info with things like compiler switches in druntime.