Merge remote-tracking branch 'upstream/master' into stable

Author: dkorpel

.htaccess

@@ -233,5 +233,8 @@ Redirect 301 /dips/1038 https://github.com/dlang/DIPs/blob/master/DIPs/accepted/
 Redirect 301 /dips/1039 https://github.com/dlang/DIPs/blob/master/DIPs/other/DIP1039.md
 Redirect 301 /dips/1040 https://github.com/dlang/DIPs/blob/master/DIPs/DIP1040.md
 Redirect 301 /dips/1041 https://github.com/dlang/DIPs/blob/master/DIPs/other/DIP1041.md
-Redirect 301 /dips/1042 https://github.com/dlang/DIPs/blob/master/DIPs/DIP1042.md
-Redirect 301 /dips/1043 https://github.com/dlang/DIPs/blob/master/DIPs/DIP1043.md
+Redirect 301 /dips/1042 https://github.com/dlang/DIPs/blob/master/DIPs/other/DIP1042.md
+Redirect 301 /dips/1043 https://github.com/dlang/DIPs/blob/master/DIPs/accepted/DIP1043.md
+Redirect 301 /dips/1044 https://github.com/dlang/DIPs/blob/master/DIPs/rejected/DIP1044.md
+Redirect 301 /dips/1045 https://github.com/dlang/DIPs/blob/master/DIPs/other/DIP1045.md
+Redirect 301 /dips/1046 https://github.com/dlang/DIPs/blob/master/DIPs/accepted/DIP1046.md

areas-of-d-usage.dd

@@ -91,9 +91,9 @@ $(AREA_SECTION3 $(LNAME2 games, Games), $(ARTICLE_FA_ICON gamepad),
 
     Many pure-D open source projects show the rising popularity
     of D among game developers.
-    Examples are the cross-platform 3D game engine
-    $(HTTP dash.circularstudios.com, Dash) and the D game development toolkit
-    $(HTTPS github.com/d-gamedev-team/gfm, gfm).
+    Examples are the 3D game engine
+    $(HTTP https://github.com/gecko0307/dagon, Dagon) and the  cross-platform D game development engine
+    $(HTTPS https://github.com/MrcSnm/HipremeEngine, HipremeEngine).
 )
 
 $(AREA_SECTION3 $(LNAME2 web, Web applications), $(ARTICLE_FA_ICON cloud),

articles/faq.dd

@@ -5,8 +5,12 @@ $(D_S $(TITLE),
         $(P The same questions keep cropping up, so the obvious thing to do is
         prepare a FAQ.)
 
-        $(P $(LINK2 http://www.digitalmars.com/d/1.0/faq.html, D 1.0 FAQ))
-        $(P $(LINK2 http://www.digitalmars.com/faq.html, C++ FAQ))
+        $(P See also:)
+
+        * $(DDLINK articles/const-faq, const(FAQ), const(FAQ)) for `const` and `immutable`.
+        * $(LINK2 http://www.prowiki.org/wiki4d/wiki.cgi?FaqRoadmap, The D wiki FAQ page)
+        * $(LINK2 http://www.digitalmars.com/d/1.0/faq.html, D 1.0 FAQ)
+        * $(LINK2 http://www.digitalmars.com/faq.html, C++ FAQ)
 
 $(H2 D 2.0 FAQ)
 
@@ -17,16 +21,6 @@ $(H2 D 2.0 FAQ)
 
         $(LI I suggested a great feature. Why was the suggestion ignored?)
 
-        $(LI Why const and immutable?)
-
-        $(LI Why the $(I names) const and immutable?)
-
-        $(LI How exactly is immutable related to multicores?)
-
-        $(LI Ok, I'm fine with immutable for safe data sharing among threads. But why do we need the uninformative const?)
-
-        $(LI Why are immutable strings favored in D 2.0?)
-
         $(LI I want to contribute to D 2.0. How can I effect that?)
 
         $(ITEMR case_range, Why doesn't the case range statement
@@ -48,9 +42,6 @@ $(H2 D 2.0 FAQ)
 $(H2 General D FAQ)
 
         $(UL
-
-        $(LI $(LINK2 http://www.prowiki.org/wiki4d/wiki.cgi?FaqRoadmap, The D wiki FAQ page)
-        with many more questions answered)
         $(LI $(LINK2 $(ROOT_DIR)comparison.html, What does D have that C++ doesn't?))
         $(ITEMR q1, Why the name D?)
         $(ITEMR q1_1, Could you change the name? D is kind of hard to search for on search engines.)
@@ -226,7 +217,7 @@ $(ITEM q4, Why is printf in D?)
         is not part of D, it is part of C's standard
         runtime library which is accessible from D.
         D's standard runtime library has
-        $(REF writefln, std,stdio)
+        $(REF writef, std,stdio)
         which is as powerful as $(LINK2 http://www.digitalmars.com/rtl/stdio.html#printf, printf)
         but is much easier to use.
         )
@@ -365,6 +356,7 @@ $(ITEM real, What is the point of 80 bit reals?)
 
 $(ITEM anonymous, How do I do anonymous struct/unions in D?)
 
+$(RUNNABLE_EXAMPLE
 -----------------------
 import std.stdio;
 
@@ -385,46 +377,74 @@ void main()
         Foo.d.offsetof);
 }
 -----------------------
+)
 
 $(ITEM printf, How do I get printf() to work with strings?)
 
-        In C, the normal way to printf a string is to use the $(B %s)
-        format:
+        $(P In C, the normal way to printf a string is to use the $(D %s)
+        format:)
 
 $(CCODE
 char s[8];
 strcpy(s, "foo");
 printf("string = '%s'\n", s);
 )
 
-        Attempting this in D, as in:
+        $(P Attempting this in D:)
 
+$(RUNNABLE_EXAMPLE_FAIL
 ---------------------------------
+import core.stdc.stdio;
 string s;
 s = "foo";
-printf("string = '%s'\n", s);
+printf("string = '%s'\n", s); // Error
 ---------------------------------
-
-        usually results in garbage being printed, or an access violation.
-        The cause is that in C, strings are terminated by a 0 character.
-        The $(B %s) format prints until a 0 is encountered.
-        In D, strings are not 0 terminated, the size is determined
+)
+        $(P The call gets flagged at compile-time (see
+        $(DDSUBLINK spec/pragma, printf, `pragma(printf)`))
+        because in general, `string` is not compatible with the `%s` specifier.
+        This prevents garbage being printed, or an access violation.)
+
+        $(P In D, a string is an array, so it has a length and a pointer.
+        In C, a string is a pointer to memory terminated by a 0 character.
+        The $(D %s) format prints until a 0 is encountered.
+        In D, strings in general are not 0-terminated, the size is determined
         by a separate length value. So, strings are printf'd using the
-        $(B %.*s) format:
+        $(D %.*s) format:)
 
+$(RUNNABLE_EXAMPLE
 ---------------------------------
+import core.stdc.stdio;
 string s;
 s = "foo";
-printf("string = '%.*s'\n", s);
+printf("string = '%.*s'\n", cast(int) s.length, s.ptr);
 ---------------------------------
+)
+        $(P which will behave as expected, for that input data.
+        There are pitfalls:)
+        * printf's $(D %.*s) will print until the length
+          is reached or a 0 is encountered, so D strings with embedded 0's
+          will only print up to the first 0.
+        * printf's length argument is an int, so ensure `s.length <= int.max`.
+
+        $(P D string literals are actually 0-terminated, so `%s` can be used
+        with the `.ptr` property and printf will work for those.
+        However, non-literal strings often are not 0-terminated:)
+
+        $(RUNNABLE_EXAMPLE
+        ---
+        import core.stdc.stdio;
+        printf("string = '%s'\n", "bar".ptr); // OK, 0-terminated
+
+        string s = "food";
+        s = s[0..3]; // foo, not 0-terminated
+        printf("string = '%.*s'\n", cast(int) s.length, s.ptr);
 
-        $(P which will behave as expected.
-        Remember, though, that printf's $(B %.*s) will print until the length
-        is reached or a 0 is encountered, so D strings with embedded 0's
-        will only print up to the first 0.
+        s ~= "ie"; // s is still not 0-terminated
+        ---
         )
 
-        $(P Of course, the easier solution is just use $(REF writefln, std, stdio)
+        $(P Of course, the easier solution is just to use $(REF writef, std, stdio)
         which works correctly with D strings.
         )
 
@@ -791,7 +811,7 @@ $(ITEM gc_1, Isn't garbage collection slow and non-deterministic?)
         However, the use of GC instead of malloc enables advanced language
         constructs (especially, more powerful array syntax), which greatly
         reduce the number of memory allocations which need to be made.
-        This can mean that GC is actually faster than explict management.
+        This can mean that GC is actually faster than explicit management.
         )
 
 $(ITEM pure, Can't a sufficiently smart compiler figure out that a function is pure automatically?)

book/dlang.org.ddoc

@@ -184,7 +184,7 @@ GLOSSARY = $(HTTP dlang.org/spec/glossary.html#$0, $0)
 GLOSSARY2 = $(HTTP dlang.org/spec/glossary.html#$1, $2)
 GNAME=<a id="$0">$(SPANC gname, $0)</a>
 GRAMMAR=$(TC pre, bnf notranslate, $0)
-GRAMMAR_INFORMATIVE=$(GRAMMAR $0)
+INFORMATIVE_GRAMMAR=$(GRAMMAR $0)
 GRAMMAR_LEX=$(GRAMMAR $0)
 GREEN=$(SPANC green, $0)
 GSELF=$(I $0)
@@ -403,7 +403,6 @@ $1
 RUNNABLE_EXAMPLE_STDIN=<code class="runnable-examples-stdin">$0</code>
 RUNNABLE_EXAMPLE_ARGS=<code class="runnable-examples-args">$0</code>
 
-SAMPLESRC=$(SPANC sample_src, $(AHTTPS github.com/dlang/dmd/blob/master/compiler/samples/$0, /dmd/compiler/samples/$0))
 SCINI=$(TC pre, scini notranslate, $0)
 SCRIPTLOAD=<script type="text/javascript" src="$1"$+></script>
 SEARCHDEFAULT_PHOBOS=

bugstats.dd

@@ -1,49 +1,35 @@
 Ddoc
 
-$(D_S Bug tracker,
+$(D_S Issue tracker,
 
 $(P
-    We use $(B Bugzilla) to track the issues for the D programming language.
+    We use $(B Github) to track the issues for the D programming language.
     $(BR)
-    The home of the D issue tracker is: $(B $(LINK https://issues.dlang.org))
+    The home of the D issue tracker is: $(B $(LINK https://github.com/dlang/dmd/issues))
 )
 
 $(P
-    You can browse through the existing bugs by project $(LINK2 https://issues.dlang.org/describecomponents.cgi?product=D, $(B here)).
+    You can browse through the existing projects $(LINK2 https://github.com/dlang, $(B here)).
 )
 
 $(P
-    If you want to search for a specific bug, you can use the $(LINK2 https://issues.dlang.org/query.cgi?format=specific, $(B search page)).
-)
-
-$(P
-    And if you want to file a new bug, you can use $(LINK2 https://issues.dlang.org/enter_bug.cgi?product=D, $(B this page)),
+    And if you want to file a new issue, you can use $(LINK2 https://github.com/dlang/dmd/issues/new, $(B this page)),
     but please $(HTTPS github.com/dlang/dmd/blob/master/CONTRIBUTING.md#reporting-bugs, check the guidelines) first.
 )
 
-$(H3 Bug Tracker Statistics)
-
-$(BOOKTABLE $(SECTION3 Current bugs <font size="-1">$(LINK2 https://issues.dlang.org/enter_bug.cgi?product=D,[report new bug])$(LINK2 https://issues.dlang.org/query.cgi,[search])</font>),
-$(DISPLAY Regression, y_axis_field=bug_severity&amp;query_format=report-table&amp;product=D&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_severity=regression)
-$(DISPLAY Blocker, y_axis_field=bug_severity&amp;query_format=report-table&amp;product=D&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_severity=blocker)
-$(DISPLAY Critical, y_axis_field=bug_severity&amp;query_format=report-table&amp;product=D&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_severity=critical)
-$(DISPLAY Major, y_axis_field=bug_severity&amp;query_format=report-table&amp;product=D&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_severity=major)
-$(DISPLAY Normal$(COMMA) minor$(COMMA) or trivial, y_axis_field=bug_severity&amp;query_format=report-table&amp;product=D&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_severity=normal&amp;bug_severity=minor&amp;bug_severity=trivial)
-$(DISPLAY Enhancement, y_axis_field=bug_severity&amp;query_format=report-table&amp;product=D&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_severity=enhancement)
-$(DISPLAY All open, y_axis_field=bug_severity&amp;query_format=report-table&amp;product=D&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_severity=normal&amp;bug_severity=minor&amp;bug_severity=trivial&amp;bug_severity=regression&amp;bug_severity=blocker&amp;bug_severity=critical&amp;bug_severity=major&amp;bug_severity=enhancement)
-$(DISPLAY All closed, y_axis_field=bug_severity&amp;query_format=report-table&amp;product=D&amp;bug_severity=normal&amp;bug_severity=minor&amp;bug_severity=trivial&amp;bug_severity=regression&amp;bug_severity=blocker&amp;bug_severity=critical&amp;bug_severity=major&amp;bug_severity=enhancement&amp;bug_status=RESOLVED&amp;bug_status=VERIFIED&amp;bug_status=CLOSED)
+$(H3 GitHub Labels)
+$(P
+    Issues & PRs are categorized using $(LINK2 https://github.com/dlang/dmd/labels, labels). Common labels include:
+    $(UL
+        $(LI $(B $(LINK2 https://github.com/dlang/dmd/labels/Severity%3AICE, Severity:ICE )) - Internal Compilation Error)
+        $(LI $(B $(LINK2 https://github.com/dlang/dmd/labels/Severity%3AEnhancement, Severity:Enhancement)) - Enhancement requests)
+        $(LI $(B $(LINK2 https://github.com/dlang/dmd/labels/Severity%3ABug%20Fix, Severity:Bug Fix)) - Bug related issues)
+        $(LI $(B $(LINK2 https://github.com/dlang/dmd/labels/Druntime, Druntime)) - Specific to Druntime)
+        $(LI $(B $(LINK2 https://github.com/dlang/dmd/labels/P1, P1)) - High Priority)
+        $(LI $(B $(LINK2 https://github.com/dlang/dmd/labels/Review%3AWIP, Review:WIP)) - Work in Progress)
+    )
 )
-
-<!-- hidden iframe to graph HTML URL, to trigger generating the image linked to below -->
-<iframe width="1" height="1" frameBorder="0" src="$(GRAPH_HTML_URL)"></iframe>
-
-$(P <center>$(LINK2 $(GRAPH_HTML_URL), <img border="1" src="$(GRAPH_IMG_URL)">)</center>)
-
 )
 
 Macros:
-  TITLE=The D Bug Tracker
-  BOOKTABLE = <center><table cellspacing="0" cellpadding="5" class="book"><caption>$1</caption>$2</table></center>
-  DISPLAY=$(TR $(TD $(LINK2 https://issues.dlang.org/buglist.cgi?$2, $1)) $(TD <iframe scrolling="no" frameborder="0" width="4.8em" height="1.4em" style="width:4.8em;height:1.4em;" vspace="0" hspace="0" marginwidth="0" marginheight="0" src="fetch-issue-cnt.php?$2&amp;format=table&amp;action=wrap&amp;ctype=csv"></iframe>))
-  GRAPH_HTML_URL=https://issues.dlang.org/reports.cgi?product=D&amp;datasets=NEW&amp;datasets=ASSIGNED&amp;datasets=REOPENED&amp;datasets=RESOLVED
-  GRAPH_IMG_URL=https://issues.dlang.org/graphs/mVH75HpydPklNqy3BSv8EvqlAOaP1WacmgYB1CsRbiM.png
+  TITLE=The D Issue Tracker

changelog/release-schedule.dd

@@ -8,22 +8,22 @@ $(UL
     $(LI Point releases are published unscheduled when important issues or regressions get fixed.)
 )
 
-$(P The release schedule for 2024 is as follows:)
+$(P The release schedule for 2025 is as follows:)
 
     $(DIVC release-schedule,
         $(TABLE
-            $(BETA_RELEASE 2024-01-01, 2.107.0)
-            $(MINOR_RELEASE 2024-02-01, 2.107.0)
-            $(BETA_RELEASE 2024-03-01, 2.108.0)
-            $(MINOR_RELEASE 2024-04-01, 2.108.0)
-            $(BETA_RELEASE 2024-05-01, 2.109.0)
-            $(MINOR_RELEASE 2024-06-01, 2.109.0)
-            $(BETA_RELEASE 2024-07-01, 2.110.0)
-            $(MINOR_RELEASE 2024-08-01, 2.110.0)
-            $(BETA_RELEASE 2024-09-01, 2.111.0)
-            $(MINOR_RELEASE 2024-10-01, 2.111.0)
-            $(BETA_RELEASE 2024-11-01, 2.112.0)
-            $(MINOR_RELEASE 2024-12-01, 2.112.0)
+            $(BETA_RELEASE 2025-01-01, 2.110.0)
+            $(MINOR_RELEASE 2025-02-01, 2.110.0)
+            $(BETA_RELEASE 2025-03-01, 2.111.0)
+            $(MINOR_RELEASE 2025-04-01, 2.111.0)
+            $(BETA_RELEASE 2025-05-01, 2.112.0)
+            $(MINOR_RELEASE 2025-06-01, 2.112.0)
+            $(BETA_RELEASE 2025-07-01, 2.113.0)
+            $(MINOR_RELEASE 2025-08-01, 2.113.0)
+            $(BETA_RELEASE 2025-09-01, 2.114.0)
+            $(MINOR_RELEASE 2025-10-01, 2.114.0)
+            $(BETA_RELEASE 2025-11-01, 2.115.0)
+            $(MINOR_RELEASE 2025-12-01, 2.115.0)
         )
     )
 )

d-keyring.gpg

@@ -1,8 +1,10 @@
 name "ddoc_preprocessor"
 description "Preprocesses source code before running Ddoc over it"
 dependency "libdparse" version="~>0.15.1"
-dependency "dmd" path="../../dmd"
-versions "DdocOptions"
+# we only need an isolated single module from DMD
+sourceFiles "../../dmd/compiler/src/dmd/cli.d"
+importPaths "source" "../../dmd/compiler/src"
+versions "DdocOptions" # for dmd.cli
 buildRequirements "disallowDeprecations"
 configuration "executable" {
 	versions "IsExecutable"

d-keyring.gpg.sig

@@ -1,7 +1,6 @@
 {
 	"fileVersion": 1,
 	"versions": {
-		"dmd": {"path":"../../dmd"},
 		"libdparse": "0.15.4",
 		"stdx-allocator": "2.77.5"
 	}