On Thursday, 31 December 2015 at 23:58:32 UTC, Craig Dillabaugh wrote:
> The deadline for the Google Summer of Code, 2016 is February 19th. Which means we have about a month and a half to put something together.  For the time being I've recycled last years projects (with one dropped so far):
>
> [...]

Deadline is getting closer, any new project ideas are welcome. Starting to get some contact from students now.

On 01/14/2016 01:56 PM, Craig Dillabaugh wrote:
> Deadline is getting closer, any new project ideas are welcome. Starting
> to get some contact from students now.

A few quick ideas:

* Bringing a parser generator library into phobos, either based on pegged or independent

* SQL parser, binder, validator

* Anything building on the strengths on D: introspection, compile-time stuff, DSL, etc.

* Improving the GC

* Theoretical work - core language semantics, proving immutable provides guarantees etc.


Andrei

On Friday, 15 January 2016 at 03:33:23 UTC, Andrei Alexandrescu wrote:
> On 01/14/2016 01:56 PM, Craig Dillabaugh wrote:
>> Deadline is getting closer, any new project ideas are welcome. Starting
>> to get some contact from students now.
>
> A few quick ideas:
>
> * Bringing a parser generator library into phobos, either based on pegged or independent
>
> * SQL parser, binder, validator
>
> * Anything building on the strengths on D: introspection, compile-time stuff, DSL, etc.
>
> * Improving the GC
>
> * Theoretical work - core language semantics, proving immutable provides guarantees etc.
>
>
> Andrei

Thanks.

On Thursday, 14 January 2016 at 18:56:21 UTC, Craig Dillabaugh wrote:
> On Thursday, 31 December 2015 at 23:58:32 UTC, Craig Dillabaugh wrote:
>> The deadline for the Google Summer of Code, 2016 is February 19th. Which means we have about a month and a half to put something together.  For the time being I've recycled last years projects (with one dropped so far):
>>
>> [...]
>
> Deadline is getting closer, any new project ideas are welcome. Starting to get some contact from students now.

It might be helpfull if they can help with:

* proper fast JSON parser (this is already worked on I think here: https://github.com/s-ludwig/std_data_json, but it seems to need a help with to finally get it to Phobos as we are constantly bit by it on public: https://github.com/kostya/benchmarks)

* same with the XML parser

* one probably crazy idea - WCF[1] interoperability for vibe.d (it might be helpfull in commercial field if one can use vibe.d as a backend server with WCF capability so .Net clients can call it directly with autogenerated protocol). But it will be a lot of work to implement all features..

[1] https://msdn.microsoft.com/en-us/library/ms731082%28v=vs.110%29.aspx

On Friday, 15 January 2016 at 03:33:23 UTC, Andrei Alexandrescu wrote:
> A few quick ideas:
>
> * Bringing a parser generator library into phobos, either based on pegged or independent
>
> * SQL parser, binder, validator
>
> * Anything building on the strengths on D: introspection, compile-time stuff, DSL, etc.
>
> * Improving the GC
>
> * Theoretical work - core language semantics, proving immutable provides guarantees etc.

* A flexible serialization framework in Phobos. std.csv could be changed to use it, and vibe.d as well as various serialization related libraries (e.g. Protocol Buffers, capnproto) would also benefit from standardization here.

On Friday, 15 January 2016 at 10:02:14 UTC, Marc Schütz wrote:
> On Friday, 15 January 2016 at 03:33:23 UTC, Andrei Alexandrescu wrote:
>> A few quick ideas:
>>
>> * Bringing a parser generator library into phobos, either based on pegged or independent
>>
>> * SQL parser, binder, validator
>>
>> * Anything building on the strengths on D: introspection, compile-time stuff, DSL, etc.
>>
>> * Improving the GC
>>
>> * Theoretical work - core language semantics, proving immutable provides guarantees etc.
>
> * A flexible serialization framework in Phobos. std.csv could be changed to use it, and vibe.d as well as various serialization related libraries (e.g. Protocol Buffers, capnproto) would also benefit from standardization here.

What about Orange?  What is preventing it from becoming part of Phobos?

https://github.com/jacob-carlborg/orange

On 1/15/16 6:58 AM, Craig Dillabaugh wrote:
> On Friday, 15 January 2016 at 10:02:14 UTC, Marc Schütz wrote:
>> On Friday, 15 January 2016 at 03:33:23 UTC, Andrei Alexandrescu wrote:
>>> A few quick ideas:
>>>
>>> * Bringing a parser generator library into phobos, either based on
>>> pegged or independent
>>>
>>> * SQL parser, binder, validator
>>>
>>> * Anything building on the strengths on D: introspection,
>>> compile-time stuff, DSL, etc.
>>>
>>> * Improving the GC
>>>
>>> * Theoretical work - core language semantics, proving immutable
>>> provides guarantees etc.
>>
>> * A flexible serialization framework in Phobos. std.csv could be
>> changed to use it, and vibe.d as well as various serialization related
>> libraries (e.g. Protocol Buffers, capnproto) would also benefit from
>> standardization here.
>
> What about Orange?  What is preventing it from becoming part of Phobos?
>
> https://github.com/jacob-carlborg/orange

I recall there has been one (or two?) unsuccessful attempts. -- Andrei

On Friday, 15 January 2016 at 12:36:32 UTC, Andrei Alexandrescu wrote:
> On 1/15/16 6:58 AM, Craig Dillabaugh wrote:
>> On Friday, 15 January 2016 at 10:02:14 UTC, Marc Schütz wrote:
>>> * A flexible serialization framework in Phobos. std.csv could be
>>> changed to use it, and vibe.d as well as various serialization related
>>> libraries (e.g. Protocol Buffers, capnproto) would also benefit from
>>> standardization here.
>>
>> What about Orange?  What is preventing it from becoming part of Phobos?
>>
>> https://github.com/jacob-carlborg/orange
>
> I recall there has been one (or two?) unsuccessful attempts. -- Andrei

Right, but it needs someone to take another stab at it. Part of the job is to gather all the requirements and look at the previous discussions as well as existing solutions.

On 01/15/2016 08:11 AM, Marc Schütz wrote:
> On Friday, 15 January 2016 at 12:36:32 UTC, Andrei Alexandrescu wrote:
>> On 1/15/16 6:58 AM, Craig Dillabaugh wrote:
>>> On Friday, 15 January 2016 at 10:02:14 UTC, Marc Schütz wrote:
>>>> * A flexible serialization framework in Phobos. std.csv could be
>>>> changed to use it, and vibe.d as well as various serialization related
>>>> libraries (e.g. Protocol Buffers, capnproto) would also benefit from
>>>> standardization here.
>>>
>>> What about Orange?  What is preventing it from becoming part of Phobos?
>>>
>>> https://github.com/jacob-carlborg/orange
>>
>> I recall there has been one (or two?) unsuccessful attempts. -- Andrei
>
> Right, but it needs someone to take another stab at it. Part of the job
> is to gather all the requirements and look at the previous discussions
> as well as existing solutions.

It would be terrific if Jacob wanted to mentor a student to work on a Phobos package starting from Orange. -- Andrei

On Friday, 15 January 2016 at 13:43:07 UTC, Andrei Alexandrescu wrote:
> On 01/15/2016 08:11 AM, Marc Schütz wrote:
>> On Friday, 15 January 2016 at 12:36:32 UTC, Andrei Alexandrescu wrote:
>>> On 1/15/16 6:58 AM, Craig Dillabaugh wrote:
>>>> On Friday, 15 January 2016 at 10:02:14 UTC, Marc Schütz wrote:
>>>>> [...]
>>>>
>>>> What about Orange?  What is preventing it from becoming part of Phobos?
>>>>
>>>> https://github.com/jacob-carlborg/orange
>>>
>>> I recall there has been one (or two?) unsuccessful attempts. -- Andrei
>>
>> Right, but it needs someone to take another stab at it. Part of the job
>> is to gather all the requirements and look at the previous discussions
>> as well as existing solutions.
>
> It would be terrific if Jacob wanted to mentor a student to work on a Phobos package starting from Orange. -- Andrei

Agreed ... Jacob?