Re: D Language Quarterly Meeting Summary for January 2021

2022-01-23 Thread Mathias LANG via Digitalmars-d-announce
On Friday, 21 January 2022 at 12:55:58 UTC, ag0aep6g wrote: On 21.01.22 13:33, Mike Parker wrote: ### Mathias Mathias would very much like to see the unification of delegates and function pointers. There was general agreement that this is a good goal to aim for. Mathias subsequently informed

Re: The DIID series (Do It In D)

2022-01-23 Thread zjh via Digitalmars-d-announce
On Sunday, 23 January 2022 at 14:23:45 UTC, Guillaume Piolat wrote: How bad really is the D ecosystem? I've started the DIID series, a good old snippet collection for you to copy/paste. Very Good!

Re: D Language Quarterly Meeting Summary for January 2021

2022-01-23 Thread Adam Ruppe via Digitalmars-d-announce
On Sunday, 23 January 2022 at 15:35:17 UTC, Paul Backus wrote: The main benefit of having multiple versions available in separate namespaces is that it allows them to coexist in the same project, which means that users can migrate their code incrementally from one to the other. Yeah, I know t

Re: D Language Quarterly Meeting Summary for January 2021

2022-01-23 Thread Paul Backus via Digitalmars-d-announce
On Sunday, 23 January 2022 at 14:53:21 UTC, Adam Ruppe wrote: On Sunday, 23 January 2022 at 14:33:26 UTC, Paul Backus wrote: Absolutely-no-breakage-ever is basically the C++ approach, and I have already explained why I think it's a bad idea, though I recognize that reasonable people can disagre

Re: D Language Quarterly Meeting Summary for January 2021

2022-01-23 Thread Adam Ruppe via Digitalmars-d-announce
On Sunday, 23 January 2022 at 14:33:26 UTC, Paul Backus wrote: Absolutely-no-breakage-ever is basically the C++ approach, and I have already explained why I think it's a bad idea, though I recognize that reasonable people can disagree on this point. My view is it isn't worth shipping mixed ver

Re: D Language Quarterly Meeting Summary for January 2021

2022-01-23 Thread Paul Backus via Digitalmars-d-announce
On Sunday, 23 January 2022 at 12:54:16 UTC, Adam D Ruppe wrote: I'm not so sure. Isn't the whole point of the versioning thing so you can use old things that haven't kept up with the latest? When it was written, sure, they used import std because that's easy and of course they want the lates

The DIID series (Do It In D)

2022-01-23 Thread Guillaume Piolat via Digitalmars-d-announce
How bad really is the D ecosystem? I've started the DIID series, a good old snippet collection for you to copy/paste. A series of article to highlight how shockingly easy some things are in D today. https://p0nce.github.io/d-idioms/#DIID-#1---Parse-XML-file https://p0nce.github.io/d-idioms/#D

Re: D Language Quarterly Meeting Summary for January 2021

2022-01-23 Thread zjh via Digitalmars-d-announce
On Saturday, 22 January 2022 at 05:43:55 UTC, Paul Backus wrote: `std.v1, std.v2` We can like this: `std->std2->std`,this is very convenient! or like C++'s `/std:c++latest`.

Re: D Language Quarterly Meeting Summary for January 2021

2022-01-23 Thread Adam D Ruppe via Digitalmars-d-announce
On Sunday, 23 January 2022 at 04:12:30 UTC, H. S. Teoh wrote: On Sun, Jan 23, 2022 at 03:24:04AM +, Paul Backus via Digitalmars-d-announce wrote: [...] The way I envision it, `std` would be the "rolling release" namespace that allows breaking changes, and if you wanted stability, you'd have

Re: D Language Quarterly Meeting Summary for January 2021

2022-01-23 Thread forkit via Digitalmars-d-announce
On Sunday, 23 January 2022 at 03:24:04 UTC, Paul Backus wrote: The way I envision it, `std` would be the "rolling release" namespace that allows breaking changes, and if you wanted stability, you'd have to explicitly depend on `std.vN`. What we currently call `std` would be renamed to `std.v1