On Sunday, 11 May 2025 at 22:06:57 UTC, Iain Buclaw wrote:
On Thursday, 8 May 2025 at 17:34:06 UTC, WB wrote:
Support for the D programming language has been updated to
version 2.111.0 of the language and run-time library. Full
changelog for this release and previous releases can be found
on the dlang.org website.
I think the D section in GCC changes always lacks details.
I think it is not enough to just reference to D changes on
some other website.
Most people do not even know D is in GCC, or by short section
in GCC changes
notes, they think that nothing is happening with D in GCC, or
it is abandoned.
I think it would be good to actually mention major work and
changes since previous 14.x and 15.1. And if possible do so in
the next versions.
Cheers.
Thanks for the suggestion. My feeling is listing all ~40 or so
"compiler changes" since the previous sync'd version (2.108)
would be a bit too much to mirror from the DMD change logs.
40 is probably not too much. But 10-15 major ones should be good
target. So some can be skipped, or just mentioned briefly without
going too much into details.
I'm also aware that almost all new features are contained
within the DMD front-end, and the actual GDC code generator
side is pretty stable - ignoring the relentless renaming of
functions and fields in upstream DMD. :-)
What about either of the following:
- Pick a few notable changes from each release. Probably
subjective.
Sounds good to me.
- Restrict to listing changes that require some explicit
support from the code generator (Placement `new`) or the
driver/cli processing (`-fpreview=safer`)
Maybe sometimes, i.e. some new flags and preview, or changes
breaking compatibility in source, or command line, would also be
nice to mention.
