On 18/07/2018 5:36 AM, Ecstatic Coder wrote:
> On Saturday, 14 July 2018 at 06:02:37 UTC, Mike Parker wrote:
>> Thanks to the sponsorship of Symmetry Investments, the D Language Foundation is happy to announce the Symmetry Autumn of Code!
>>
>> We're looking for three university students to hack on D this autumn, from September - January. We're also in search of potential mentors and ideas for student projects. Head to the Symmetry Autumn of Code page for the details.
>>
>> Spread the word!
>>
>> https://dlang.org/blog/symmetry-autumn-of-code/
> 
> I'd suggest adding the following to SAOC 2018 project proposals :
> 
> 1/ adding a Go-like http module to the standard library
> 2/ adding Go-like async IO management to the standard library, i.e. fibers communicating through blocking channels

Until we get an event loop in druntime, both of these options are off the table.

On Saturday, 14 July 2018 at 06:02:37 UTC, Mike Parker wrote:
> Thanks to the sponsorship of Symmetry Investments, the D Language Foundation is happy to announce the Symmetry Autumn of Code!
>
> We're looking for three university students to hack on D this autumn, from September - January. We're also in search of potential mentors and ideas for student projects. Head to the Symmetry Autumn of Code page for the details.
>
> Spread the word!
>
> https://dlang.org/blog/symmetry-autumn-of-code/

Proposal: Multi IDE debugger support (for windows)

Mago, the debug engine used in VisualD, has also a tool called Mago-MI which
has a GDB compatible interface. Therefore you can use on Windows Mago-MI as
replacement for GDB.
Several IDEs uses this feature to enable debugging with 1 code line for Windows/Linux/MacOS.
It is used in experimental state in IntelliJ, also there is support in Visual Studio Code
and of course DLangIDE for which it was originally built.

There are several issues which could be addressed in Symmetry Autumn of Code:

- Mago-MI is written in C++. This makes bug solving hard. Rewriting of Mago-MI to D might
make sense.

- While the installation of Mago-MI is easy if you want to debug OMF executables it is very hard if you want to debug COFF executables. You need another executable from Mago,
you have to register DLLs via regserv and you manually have to create a registry entry.
An installation procedure for installing Mago-MI would be great.

- There are some bugs in Mago-MI / and DMD (wrong debug information) which makes debugging hard. (https://github.com/rainers/mago/issues/21, https://github.com/rainers/mago/issues/23). Also Mago-Mi misses features (https://github.com/rainers/mago/issues/14). There are more bugs but not investigated so far.

- As Visual Studio Code is already is already a topic for DLang Foundation, using this as reference user of Mago-MI would make sense.


While this proposal seems only windows related, the nature of Mago-Mi is to enable IDEs having 1 code line for debugging on Windows/Linux/MacOS. Therefore overall investing into this topic is good for all platforms.

Kind regards
André

On Saturday, 14 July 2018 at 06:02:37 UTC, Mike Parker wrote:
> Thanks to the sponsorship of Symmetry Investments, the D Language Foundation is happy to announce the Symmetry Autumn of Code!
>
> We're looking for three university students to hack on D this autumn, from September - January. We're also in search of potential mentors and ideas for student projects. Head to the Symmetry Autumn of Code page for the details.
>
> Spread the word!
>
> https://dlang.org/blog/symmetry-autumn-of-code/

Another proposal: Adding D support to gRPC

I started to add D support to gRPC but paused it due to lack of knowledge and time.
One solution would be to add a D wrapper to https://github.com/grpc/grpc/tree/master/src by making use of the C interface of gRPC (https://github.com/grpc/grpc/tree/master/include/grpc).

As template e.g. C++ or python could be used (https://github.com/grpc/grpc/tree/master/src).

Kind regards
André

On Wednesday, 18 July 2018 at 10:35:04 UTC, Andre Pany wrote:
>
> Proposal: Multi IDE debugger support (for windows)
> [snip]

This is a good idea too.

On Wednesday, 18 July 2018 at 03:19:53 UTC, rikki cattermole wrote:
> On 18/07/2018 5:36 AM, Ecstatic Coder wrote:
>> On Saturday, 14 July 2018 at 06:02:37 UTC, Mike Parker wrote:
>>> Thanks to the sponsorship of Symmetry Investments, the D Language Foundation is happy to announce the Symmetry Autumn of Code!
>>>
>>> We're looking for three university students to hack on D this autumn, from September - January. We're also in search of potential mentors and ideas for student projects. Head to the Symmetry Autumn of Code page for the details.
>>>
>>> Spread the word!
>>>
>>> https://dlang.org/blog/symmetry-autumn-of-code/
>> 
>> I'd suggest adding the following to SAOC 2018 project proposals :
>> 
>> 1/ adding a Go-like http module to the standard library
>> 2/ adding Go-like async IO management to the standard library, i.e. fibers communicating through blocking channels
>
> Until we get an event loop in druntime, both of these options are off the table.

Sad.

Then I'd suggest to add the event loop implementation to SAOC 2018 too, because the absence of a default http module in D's standard library may have very good justifications, but I'm still convinced that it doesn't help when trying to "sell" it to modern developers, considering that nowadays MANY of the applications they will develop in a professional facility will have to integrate http code to access or update the company's data.

On 18/07/2018 10:53 PM, Ecstatic Coder wrote:
> On Wednesday, 18 July 2018 at 03:19:53 UTC, rikki cattermole wrote:
>> On 18/07/2018 5:36 AM, Ecstatic Coder wrote:
>>> On Saturday, 14 July 2018 at 06:02:37 UTC, Mike Parker wrote:
>>>> Thanks to the sponsorship of Symmetry Investments, the D Language Foundation is happy to announce the Symmetry Autumn of Code!
>>>>
>>>> We're looking for three university students to hack on D this autumn, from September - January. We're also in search of potential mentors and ideas for student projects. Head to the Symmetry Autumn of Code page for the details.
>>>>
>>>> Spread the word!
>>>>
>>>> https://dlang.org/blog/symmetry-autumn-of-code/
>>>
>>> I'd suggest adding the following to SAOC 2018 project proposals :
>>>
>>> 1/ adding a Go-like http module to the standard library
>>> 2/ adding Go-like async IO management to the standard library, i.e. fibers communicating through blocking channels
>>
>> Until we get an event loop in druntime, both of these options are off the table.
> 
> Sad.
> 
> Then I'd suggest to add the event loop implementation to SAOC 2018 too, because the absence of a default http module in D's standard library may have very good justifications, but I'm still convinced that it doesn't help when trying to "sell" it to modern developers, considering that nowadays MANY of the applications they will develop in a professional facility will have to integrate http code to access or update the company's data.

I've said, that if we get signatures, I'll build the damn thing myself.
Signatures give a very lightweight vtable implementation while also giving conceptual representation of structs+classes.

Which for an event loop, is a very desirable thing to have. But alas, I'm waiting on my named parameter DIP and seeing where that goes, before continuing work on signatures.

> I've said, that if we get signatures, I'll build the damn thing myself.
> Signatures give a very lightweight vtable implementation while also giving conceptual representation of structs+classes.
>
> Which for an event loop, is a very desirable thing to have. But alas, I'm waiting on my named parameter DIP and seeing where that goes, before continuing work on signatures.

Thanks for the clear explanations.

Glad to know that you're on this.

I hope the importance of your work for D's "competivity" will be truly recognized.

On Saturday, 14 July 2018 at 07:30:26 UTC, Joakim wrote:
> On Saturday, 14 July 2018 at 06:02:37 UTC, Mike Parker wrote:
>> Thanks to the sponsorship of Symmetry Investments, the D Language Foundation is happy to announce the Symmetry Autumn of Code!
>>
>> We're looking for three university students to hack on D this autumn, from September - January. We're also in search of potential mentors and ideas for student projects. Head to the Symmetry Autumn of Code page for the details.
>>
>> Spread the word!
>>
>> https://dlang.org/blog/symmetry-autumn-of-code/
>
> "join us" for
> "submit an application" -> apply (confusing otherwise)
>
> Maybe sum up and make clear that each student can earn between $3000-4000, instead of capped at $1k.

This is why I suggested stating the total sum clearly:

"20 hours/week for four months for a salary of $1000 seems kind of crappy. Am I reading this wrong?"
https://www.reddit.com/r/programming/comments/8yram3/comment/e2gttg2

You're currently requiring people to read carefully and do the math to understand this: most people do neither.

On Saturday, 14 July 2018 at 06:02:37 UTC, Mike Parker wrote:
> Thanks to the sponsorship of Symmetry Investments, the D Language Foundation is happy to announce the Symmetry Autumn of Code!
>
> We're looking for three university students to hack on D this autumn, from September - January. We're also in search of potential mentors and ideas for student projects. Head to the Symmetry Autumn of Code page for the details.
>
> Spread the word!
>
> https://dlang.org/blog/symmetry-autumn-of-code/

I'm interested in the "Graphics library for resource constrained embedded systems" project and have some spare time this autumn, but I have some questions:
- Does this project aim at creating a hardware-agnostic rasterizer supporting a few primitives like https://skia.org/ or implementing a full GUI library like emWin rendering widget and handling I/O events such as mouse? The latter one sounds a little bit challenging to finish in four months
- In the past year I primarily wrote C++ and don't have much experiences with production-level D programming, can I get involved into this program?

Thanks

> I'm interested in the "Graphics library for resource constrained embedded systems" project and have some spare time this autumn, but I have some questions:
> - Does this project aim at creating a hardware-agnostic rasterizer supporting a few primitives like https://skia.org/ or implementing a full GUI library like emWin rendering widget and handling I/O events such as mouse? The latter one sounds a little bit challenging to finish in four months
> - In the past year I primarily wrote C++ and don't have much experiences with production-level D programming, can I get involved into this program?
>
> Thanks

IMHO no need to reinvent the wheel for that.

You can probably do both in four months, if you just "port" (separately) and bind the code of the two following libraries :
1/ swGL (https://github.com/h0MER247/swGL)
2/ Nuklear (https://github.com/vurtun/nuklear)

They have a very open design, and are already quite well optimized for speed and memory consumption.

Moreover this would allow the D port of the Nuklear library to also use a hardware accelerated renderer on desktop platforms.

Nice isn't it ?

And I'd be glad to mentor you on this :)