Hi all,

the DConf hackathon isn’t a hackathon in the traditional sense. It is intended as a day for _collaboratively_ focusing on long-lasting problems and pain points in the D ecosystem, planning upcoming features or DIPs, and creation of a rough roadmap for the next months.
Of course, any D hackers who wish to simply progress their own personal projects are welcome too!

Experience has shown that in large groups too much time is wasted on giving a voice to everyone, whereas for tiny groups chances are that it takes too long to get the ball rolling.
Hence, a group size of four or five D hackers is recommended.

Below you can find a list of themes with a short abstract and a couple of ideas. The abstracts and ideas are intended to get you started and guide you. Please feel free to _add your own ideas_ and _add your names_ next to them so that people can ping you (IRC, email, and other IM handles might be handy as well). Of course, you can add your name to multiple projects.
On Sunday the first half an hour will be used to finalize the group forming. All existing groups and persons with an idea, but without a group can pitch their idea shortly (one minute max, no slides) and thus find other motivated D hackers.


https://docs.google.com/document/d/1L5edu6LLj3Afa3tPgqk-aX-fErwr7sPj37Dt5avoc5w/edit#

In short I want Phobos to have an image library and long with it a windowing lib (but lets ignore that last part for now).
I welcome people stealing and creating a competing ideas for anything in [0] and [1] that I have.

Alternatively you can also create PR's for anything there as well.
There is also [2] which is the start of my fixed-sized linear algebra library for game development.

Of note is my managed memory concept, it needs a full rewrite. I have yet to be able to use it to its full power with its managers (e.g. data structure knowing when memory is ready to die).

There is a serializer in[1] that could do with a couple of iterations in becoming faster and more feature full.

I will try my best to be available via IRC and on the N.G. but well New Zealand time zones and all that. If you have any questions or want some assistance, hit me up!

Now let's destruct these ideas.

[0] https://github.com/rikkimax/alphaPhobos/tree/master/source/std/experimental
[1] https://github.com/Devisualization/spew/tree/master/src/base/cf/spew/serialization
[2] https://gist.github.com/rikkimax/f5c0accd3463d52fda524f1f929b29ab

On 5/4/17 15:32, Seb wrote:
> Hi all,
>
> the DConf hackathon isn’t a hackathon in the traditional sense. It is
> intended as a day for _collaboratively_ focusing on long-lasting
> problems and pain points in the D ecosystem, planning upcoming features
> or DIPs, and creation of a rough roadmap for the next months.
> Of course, any D hackers who wish to simply progress their own personal
> projects are welcome too!
>
> Experience has shown that in large groups too much time is wasted on
> giving a voice to everyone, whereas for tiny groups chances are that it
> takes too long to get the ball rolling.
> Hence, a group size of four or five D hackers is recommended.
>
> Below you can find a list of themes with a short abstract and a couple
> of ideas. The abstracts and ideas are intended to get you started and
> guide you. Please feel free to _add your own ideas_ and _add your names_
> next to them so that people can ping you (IRC, email, and other IM
> handles might be handy as well). Of course, you can add your name to
> multiple projects.
> On Sunday the first half an hour will be used to finalize the group
> forming. All existing groups and persons with an idea, but without a
> group can pitch their idea shortly (one minute max, no slides) and thus
> find other motivated D hackers.
>
>
> https://docs.google.com/document/d/1L5edu6LLj3Afa3tPgqk-aX-fErwr7sPj37Dt5avoc5w/edit#
>

From the Phobos wishlist:
I am working an a generic SQL database interface. If anybody is interested in helping out I have a small amount of code that shows the general design direction I've taken so far. We can discuss the design and collaboratively hack out a prototype.

The current code is here: https://github.com/LightBender/std.experimental.database.sql

-- 
Adam Wilson
IRC: LightBender
import quiet.dlang.dev;

On 04/05/2017 3:22 PM, Adam Wilson wrote:
> On 5/4/17 15:32, Seb wrote:
>> Hi all,
>>
>> the DConf hackathon isn’t a hackathon in the traditional sense. It is
>> intended as a day for _collaboratively_ focusing on long-lasting
>> problems and pain points in the D ecosystem, planning upcoming features
>> or DIPs, and creation of a rough roadmap for the next months.
>> Of course, any D hackers who wish to simply progress their own personal
>> projects are welcome too!
>>
>> Experience has shown that in large groups too much time is wasted on
>> giving a voice to everyone, whereas for tiny groups chances are that it
>> takes too long to get the ball rolling.
>> Hence, a group size of four or five D hackers is recommended.
>>
>> Below you can find a list of themes with a short abstract and a couple
>> of ideas. The abstracts and ideas are intended to get you started and
>> guide you. Please feel free to _add your own ideas_ and _add your names_
>> next to them so that people can ping you (IRC, email, and other IM
>> handles might be handy as well). Of course, you can add your name to
>> multiple projects.
>> On Sunday the first half an hour will be used to finalize the group
>> forming. All existing groups and persons with an idea, but without a
>> group can pitch their idea shortly (one minute max, no slides) and thus
>> find other motivated D hackers.
>>
>>
>> https://docs.google.com/document/d/1L5edu6LLj3Afa3tPgqk-aX-fErwr7sPj37Dt5avoc5w/edit#
>>
>>
>
> From the Phobos wishlist:
> I am working an a generic SQL database interface. If anybody is
> interested in helping out I have a small amount of code that shows the
> general design direction I've taken so far. We can discuss the design
> and collaboratively hack out a prototype.
>
> The current code is here:
> https://github.com/LightBender/std.experimental.database.sql

Looking at that I think focusing on describing of tables ext. would be a good first step. I worry that it won't be very flexible memory management or serialization wise.

I just added two things:

1) error messages, which are code intensive but a HUGE payoff in productivity (and thus marketing)

and 2) Opposite attributes, which are trivial to implement but painful to get merged.


I think dconf is a good opportunity for you guys to get things like #2 actually merged. No more waiting for months for a review, discuss it right there and have an in-person decision to go or not go. Merge immediately without additional delay.

On Thursday, 4 May 2017 at 14:53:34 UTC, Adam D. Ruppe wrote:
> I just added two things:
>
> 1) error messages, which are code intensive but a HUGE payoff in productivity (and thus marketing)
>
> and 2) Opposite attributes, which are trivial to implement but painful to get merged.
>
>
> I think dconf is a good opportunity for you guys to get things like #2 actually merged. No more waiting for months for a review, discuss it right there and have an in-person decision to go or not go. Merge immediately without additional delay.

I just had a vision:

pragma(pushAttributes);
@safe: void foo();
pragma(popAttributes);
void notsafeanymore();

No need for reverse for each attribute (and new attributes in the future).

On 04/05/2017 4:29 PM, OoopsAgain wrote:
> On Thursday, 4 May 2017 at 14:53:34 UTC, Adam D. Ruppe wrote:
>> I just added two things:
>>
>> 1) error messages, which are code intensive but a HUGE payoff in
>> productivity (and thus marketing)
>>
>> and 2) Opposite attributes, which are trivial to implement but painful
>> to get merged.
>>
>>
>> I think dconf is a good opportunity for you guys to get things like #2
>> actually merged. No more waiting for months for a review, discuss it
>> right there and have an in-person decision to go or not go. Merge
>> immediately without additional delay.
>
> I just had a vision:
>
> pragma(pushAttributes);
> @safe: void foo();
> pragma(popAttributes);
> void notsafeanymore();
>
> No need for reverse for each attribute (and new attributes in the future).

So:

@safe {
	void foo();
}

void notsafeanymore();

On Thursday, 4 May 2017 at 15:40:57 UTC, rikki cattermole wrote:
> On 04/05/2017 4:29 PM, OoopsAgain wrote:
>> On Thursday, 4 May 2017 at 14:53:34 UTC, Adam D. Ruppe wrote:
>>> [...]
>>
>> I just had a vision:
>>
>> pragma(pushAttributes);
>> @safe: void foo();
>> pragma(popAttributes);
>> void notsafeanymore();
>>
>> No need for reverse for each attribute (and new attributes in the future).
>
> So:
>
> @safe {
> 	void foo();
> }
>
> void notsafeanymore();

I suppose this would be fundamentally implemented in this way:  new scope with scope attridfgjlkdg,;

On 5/4/17 16:33, rikki cattermole wrote:
> On 04/05/2017 3:22 PM, Adam Wilson wrote:
>> On 5/4/17 15:32, Seb wrote:
>>> Hi all,
>>>
>>> the DConf hackathon isn’t a hackathon in the traditional sense. It is
>>> intended as a day for _collaboratively_ focusing on long-lasting
>>> problems and pain points in the D ecosystem, planning upcoming features
>>> or DIPs, and creation of a rough roadmap for the next months.
>>> Of course, any D hackers who wish to simply progress their own personal
>>> projects are welcome too!
>>>
>>> Experience has shown that in large groups too much time is wasted on
>>> giving a voice to everyone, whereas for tiny groups chances are that it
>>> takes too long to get the ball rolling.
>>> Hence, a group size of four or five D hackers is recommended.
>>>
>>> Below you can find a list of themes with a short abstract and a couple
>>> of ideas. The abstracts and ideas are intended to get you started and
>>> guide you. Please feel free to _add your own ideas_ and _add your names_
>>> next to them so that people can ping you (IRC, email, and other IM
>>> handles might be handy as well). Of course, you can add your name to
>>> multiple projects.
>>> On Sunday the first half an hour will be used to finalize the group
>>> forming. All existing groups and persons with an idea, but without a
>>> group can pitch their idea shortly (one minute max, no slides) and thus
>>> find other motivated D hackers.
>>>
>>>
>>> https://docs.google.com/document/d/1L5edu6LLj3Afa3tPgqk-aX-fErwr7sPj37Dt5avoc5w/edit#
>>>
>>>
>>>
>>
>> From the Phobos wishlist:
>> I am working an a generic SQL database interface. If anybody is
>> interested in helping out I have a small amount of code that shows the
>> general design direction I've taken so far. We can discuss the design
>> and collaboratively hack out a prototype.
>>
>> The current code is here:
>> https://github.com/LightBender/std.experimental.database.sql
>
> Looking at that I think focusing on describing of tables ext. would be a
> good first step. I worry that it won't be very flexible memory
> management or serialization wise.
>

It's definitely the hardest problem to solve. Obviously we could start with a brute force approach (box everything like ADO.NET does) for the sake of getting started and then work on improving it later. For now I compromised and used Variant, which should be sufficient for most cases right now. (See latest commit) I am using Classes and Dynamic Arrays so it's not @nogc yet, but this is something that can be improved over time. There is no reason that this could not use the new Allocators API at a later date.

I'm not looking for inclusion into Phobos during the DConf Hackathon, but I would like to block out something that we can start using.

-- 
Adam Wilson
IRC: LightBender
import quiet.dlang.dev;

On Thursday, 4 May 2017 at 13:32:21 UTC, Seb wrote:
> Hi all,
>
> the DConf hackathon isn’t a hackathon in the traditional sense. It is intended as a day for _collaboratively_ focusing on long-lasting problems and pain points in the D ecosystem, planning upcoming features or DIPs, and creation of a rough roadmap for the next months.
> Of course, any D hackers who wish to simply progress their own personal projects are welcome too!
>
> [...]

Please don't forget to put your names next to ideas that you would like to work on ;-)