On 01/04/2017 08:06 PM, Dibyendu Majumdar wrote:
> C++ integration has disappeared? Is this now "done"?

We have a student on that. I've added a line for that to the doc. -- Andrei

On 01/04/2017 11:43 PM, Basile B. wrote:
> 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.

Is this formalized in bugzilla? -- Andrei

On 01/05/2017 05:43 AM, Basile B. wrote:
> 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.

That's already what we decided in September, so where is the problem? http://forum.dlang.org/post/ymkehalxcigswvltlfjj@forum.dlang.org https://github.com/dlang/dmd/pull/6111

On 01/05/2017 11:00 AM, Basile B. wrote:
> 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

This is superfluous by now. We figured that allowing access to private
fields wouldn't clash with important optimizations, so it can be allowed
via traits.
The visibility of allMembers was adjusted in
https://github.com/dlang/dmd/pull/6078.
All access checks will go away once the visibility changes have been
fully deprecated. So far those changes were adopted fairly slow (not
even phobos has fixed them all), hence we haven't yet switched over to
the new visibility semantics.

-Martin

On 01/06/2017 11:09 PM, Anton 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
> 
> 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
> ...

Thanks, we are aware of the various limitations, hence it'll be a major priority to improve the site. Improving search and tagging is one bigger aspect of that, distinguishing high quality packages another one.

-Martin

On 01/05/2017 11:45 PM, Sönke Ludwig wrote:
> 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

I think there won't be much discussions about the goals (maybe about the priorities). Many people come up with the same ideas to resolve the pain points.

Actually I have a draft for a renewed site, will look at implementing
that (hopefully with Sebastian, Söhnke, and others) in the next few month.

So far haven't found an angle at breaking up the story though, it's fairly intermingled. If we can't do it incrementally, that would require a bit more orchestration for a major rerelease.

- better search, also on README bodies (e.g. sqlite FTS)
- tagging instead of hierarchical categories
- ranking (downloads, stars, dependents, testing...)
- better landing page (big search form and listing 10 top, 10 trending,
and 10 newest packages)
- better GH integration

Personally would approach this mid/end of March, but if enough people have time we could do it earlier.

https://dlang.slack.com/messages/dub/

On 01/07/2017 02:55 PM, Martin Nowak wrote:
> On 01/05/2017 11:00 AM, Basile B. wrote:
>> 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
>
> This is superfluous by now. We figured that allowing access to private
> fields wouldn't clash with important optimizations, so it can be allowed
> via traits.
> The visibility of allMembers was adjusted in
> https://github.com/dlang/dmd/pull/6078.
> All access checks will go away once the visibility changes have been
> fully deprecated. So far those changes were adopted fairly slow (not
> even phobos has fixed them all), hence we haven't yet switched over to
> the new visibility semantics.
>
> -Martin

Oh, now I remember. Yes, introspection works in "sudo" mode - all information is available to it, including what's private and what isn't :o). Thanks Martin for fielding this and other questions. -- Andrei

On Saturday, 7 January 2017 at 20:10:17 UTC, Martin Nowak wrote:
> I think there won't be much discussions about the goals (maybe about the priorities). Many people come up with the same ideas to resolve the pain points.
>
> Actually I have a draft for a renewed site, will look at implementing
> that (hopefully with Sebastian, Söhnke, and others) in the next few month.
>
> So far haven't found an angle at breaking up the story though, it's fairly intermingled. If we can't do it incrementally, that would require a bit more orchestration for a major rerelease.
>
> - better search, also on README bodies (e.g. sqlite FTS)
> - tagging instead of hierarchical categories
> - ranking (downloads, stars, dependents, testing...)
> - better landing page (big search form and listing 10 top, 10 trending,
> and 10 newest packages)
> - better GH integration

Maybe something to add ( for new users ) is something similar to:

http://rustbyexample.com/

Easy to use, lots of information, simple tasks that involve interaction for the user, feedback on success.

On Saturday, 7 January 2017 at 23:33:45 UTC, Benjiro wrote:
> Maybe something to add ( for new users ) is something similar to:
>
> http://rustbyexample.com/
>
> Easy to use, lots of information, simple tasks that involve interaction for the user, feedback on success.

Do you know about the existing Dlang Tour?

https://tour.dlang.org

PRs/Issues to improve it are welcome

Its translation into a couple of languages is WIP:

https://github.com/dlang-tour

On Saturday, 7 January 2017 at 15:58:43 UTC, Andrei Alexandrescu wrote:
> On 01/04/2017 08:06 PM, Dibyendu Majumdar wrote:
>> C++ integration has disappeared? Is this now "done"?
>
> We have a student on that. I've added a line for that to the doc. -- Andrei

Cool. C++ integration would be a big plus for D so it would be great if this feature was completed to a defined standard - by this I mean that there ought to be documentation on what works, but more importantly, what doesn't, so that users don't have to try to work this out by trial and error.

Regards
Dibyendu