The Symmetry Autumn of Code 2019 application selection process has come to an end. This year, we've got five projects instead of three. Congratulations to everyone who was selected! You can read about them and their projects over at the D Blog:

https://dlang.org/blog/2019/08/25/saoc-2019-projects-and-participants/

Reddit:
https://www.reddit.com/r/d_language/comments/cv8jtd/saoc_2019_projects_and_participants/

On Sunday, 25 August 2019 at 13:38:24 UTC, Mike Parker wrote:
> The Symmetry Autumn of Code 2019 application selection process has come to an end. This year, we've got five projects instead of three. Congratulations to everyone who was selected! You can read about them and their projects over at the D Blog:
>
> https://dlang.org/blog/2019/08/25/saoc-2019-projects-and-participants/
>
> Reddit:
> https://www.reddit.com/r/d_language/comments/cv8jtd/saoc_2019_projects_and_participants/

Kudos to all 8 for trying! The project seem interesting.

I'd like to focus on the MLIR project since I have been looking MLIR for the
last month.

I belive this a project with big potential if MLIR succeeds.

Roberto congratulations!
I don't know how much experience you have with compilers or LDC. I'm sure
Nicholas will be there to help you but here are some suggestions.

There are a bunch of talks that I feel like focus more on the goals of MLIR
and not the practical side (the goals are important, don't get me wrong).

Aside from the general README etc., here's one tutorial I like [1]. I think it's a good introduction.
This talk [2] is mostly good too.

For LDC, there's of course the dlang forum LDC group, but also
don't forget the Gitter: http://gitter.im/ldc-developers/main.

This is the main discussion thread for LDC. Don't hesitate to ask questions there!

[1] https://github.com/tensorflow/mlir/blob/master/g3doc/Tutorials/Toy/Ch-1.md
[2] https://www.youtube.com/watch?v=cyICUIZ56wQ

On Sunday, 25 August 2019 at 13:38:24 UTC, Mike Parker wrote:
> The Symmetry Autumn of Code 2019 application selection process has come to an end. This year, we've got five projects instead of three. Congratulations to everyone who was selected! You can read about them and their projects over at the D Blog:
>
> https://dlang.org/blog/2019/08/25/saoc-2019-projects-and-participants/
>
> Reddit:
> https://www.reddit.com/r/d_language/comments/cv8jtd/saoc_2019_projects_and_participants/

I need to apologize to Laeeth and Manu. I mistakenly attributed the stl-containers repository to Suleyman:

https://github.com/dlang-cpp-interop/stl-containers/

That was a major oversight on my part.

On Sunday, 25 August 2019 at 13:38:24 UTC, Mike Parker wrote:
> ...
> Solve Dependency Hell:
> This is considered as a crucial first step in making Phobos available via the DUB registry

I'm guessing this means we might even be able to use multiple versions of Phobos one day. However before we do that, we will really need to fix the use of globals in Phobos.

On Sunday, 25 August 2019 at 13:38:24 UTC, Mike Parker wrote:
> The Symmetry Autumn of Code 2019 application selection process has come to an end. This year, we've got five projects instead of three. Congratulations to everyone who was selected! You can read about them and their projects over at the D Blog:
>
> https://dlang.org/blog/2019/08/25/saoc-2019-projects-and-participants/
>
> Reddit:
> https://www.reddit.com/r/d_language/comments/cv8jtd/saoc_2019_projects_and_participants/

Congratulations to the selected projects, and Good luck!

On 2019-08-26 05:55, Andrej Mitrovic wrote:

> I'm guessing this means we might even be able to use multiple versions of Phobos one day. However before we do that, we will really need to fix the use of globals in Phobos.

I don't think that's necessary. All symbols will have the version be part of the mangled name.

-- 
/Jacob Carlborg

On Monday, 26 August 2019 at 11:03:51 UTC, Jacob Carlborg wrote:
> On 2019-08-26 05:55, Andrej Mitrovic wrote:
>
>> I'm guessing this means we might even be able to use multiple versions of Phobos one day. However before we do that, we will really need to fix the use of globals in Phobos.
>
> I don't think that's necessary. All symbols will have the version be part of the mangled name.

so, the target of project is to make mangled name for using by app 2+ version of one lib/module?
cuz in that case u cannot fix situation when libV1.obj will land to libV2 somehow (through globals, AA.. ) and binary implementation is different. probably will be panic, data loss and other bad things.

On Sunday, 25 August 2019 at 13:38:24 UTC, Mike Parker wrote:
> The Symmetry Autumn of Code 2019 application selection process has come to an end. This year, we've got five projects instead of three. Congratulations to everyone who was selected! You can read about them and their projects over at the D Blog:
>
> https://dlang.org/blog/2019/08/25/saoc-2019-projects-and-participants/

Sorry, I haven't been following. Don't we already have an implementation of the "Create a CI or other infrastructure for measuring D’s progress and performance" project? I just haven't been maintaining it because there hasn't been a lot of interest in it while it was being maintained.

Here's the original blog post:

https://blog.thecybershadow.net/2015/05/05/is-d-slim-yet/

I'll give it a kick and get it back online if there is interest. Seems wasteful to reimplement it from scratch, though.

On Monday, 26 August 2019 at 18:51:54 UTC, Vladimir Panteleev wrote:

> Here's the original blog post:
>
> https://blog.thecybershadow.net/2015/05/05/is-d-slim-yet/
>
> I'll give it a kick and get it back online if there is interest. Seems wasteful to reimplement it from scratch, though.

It's great to see this back up and running.  The compile-time data is quite interesting.  Is there any way to identify a particular offending commit. The commits identified in the data points on the chart don't seem to be precise.

Mike

On Tuesday, 27 August 2019 at 09:08:58 UTC, Mike Franklin wrote:
> It's great to see this back up and running.  The compile-time data is quite interesting.  Is there any way to identify a particular offending commit. The commits identified in the data points on the chart don't seem to be precise.

It will eventually zero in to commit-level accuracy after it's been running for a while. I cleared the database as the last time it was running, it was on another CPU, so the timings are going to be different. (Still need to decide on a way to measure execution time in some deterministic way.)