Add parsetree support for wildcards in simple expressions

.depend

@@ -155,11 +155,13 @@ utils/local_store.cmx : \
     utils/local_store.cmi
 utils/local_store.cmi :
 utils/misc.cmo : \
+    utils/utf8_lexeme.cmi \
     utils/format_doc.cmi \
     utils/config.cmi \
     utils/build_path_prefix_map.cmi \
     utils/misc.cmi
 utils/misc.cmx : \
+    utils/utf8_lexeme.cmx \
     utils/format_doc.cmx \
     utils/config.cmx \
     utils/build_path_prefix_map.cmx \
@@ -216,6 +218,11 @@ utils/terminfo.cmo : \
 utils/terminfo.cmx : \
     utils/terminfo.cmi
 utils/terminfo.cmi :
+utils/utf8_lexeme.cmo : \
+    utils/utf8_lexeme.cmi
+utils/utf8_lexeme.cmx : \
+    utils/utf8_lexeme.cmi
+utils/utf8_lexeme.cmi :
 utils/warnings.cmo : \
     utils/misc.cmi \
     utils/format_doc.cmi \
@@ -414,6 +421,7 @@ parsing/docstrings.cmi : \
     parsing/location.cmi
 parsing/lexer.cmo : \
     utils/warnings.cmi \
+    utils/utf8_lexeme.cmi \
     parsing/parser.cmi \
     utils/misc.cmi \
     parsing/location.cmi \
@@ -422,6 +430,7 @@ parsing/lexer.cmo : \
     parsing/lexer.cmi
 parsing/lexer.cmx : \
     utils/warnings.cmx \
+    utils/utf8_lexeme.cmx \
     parsing/parser.cmx \
     utils/misc.cmx \
     parsing/location.cmx \
@@ -567,13 +576,15 @@ parsing/syntaxerr.cmi : \
     parsing/location.cmi
 parsing/unit_info.cmo : \
     utils/warnings.cmi \
+    utils/utf8_lexeme.cmi \
     utils/misc.cmi \
     parsing/location.cmi \
     utils/load_path.cmi \
     utils/config.cmi \
     parsing/unit_info.cmi
 parsing/unit_info.cmx : \
     utils/warnings.cmx \
+    utils/utf8_lexeme.cmx \
     utils/misc.cmx \
     parsing/location.cmx \
     utils/load_path.cmx \
@@ -731,6 +742,7 @@ typing/datarepr.cmi : \
     typing/data_types.cmi
 typing/env.cmo : \
     utils/warnings.cmi \
+    utils/utf8_lexeme.cmi \
     parsing/unit_info.cmi \
     typing/typing_recovery.cmi \
     typing/types.cmi \
@@ -758,6 +770,7 @@ typing/env.cmo : \
     typing/env.cmi
 typing/env.cmx : \
     utils/warnings.cmx \
+    utils/utf8_lexeme.cmx \
     parsing/unit_info.cmx \
     typing/typing_recovery.cmx \
     typing/types.cmx \
@@ -1137,17 +1150,17 @@ typing/mtype.cmi : \
     typing/ident.cmi \
     typing/env.cmi
 typing/oprint.cmo : \
+    utils/utf8_lexeme.cmi \
     parsing/pprintast.cmi \
     typing/outcometree.cmi \
-    utils/misc.cmi \
     parsing/lexer.cmi \
     utils/format_doc.cmi \
     parsing/asttypes.cmi \
     typing/oprint.cmi
 typing/oprint.cmx : \
+    utils/utf8_lexeme.cmx \
     parsing/pprintast.cmx \
     typing/outcometree.cmi \
-    utils/misc.cmx \
     parsing/lexer.cmx \
     utils/format_doc.cmx \
     parsing/asttypes.cmx \
@@ -4072,10 +4085,12 @@ asmcomp/selection.cmx : \
 asmcomp/stackframe.cmo : \
     asmcomp/stackframegen.cmi \
     asmcomp/mach.cmi \
+    utils/config.cmi \
     asmcomp/stackframe.cmi
 asmcomp/stackframe.cmx : \
     asmcomp/stackframegen.cmx \
     asmcomp/mach.cmx \
+    utils/config.cmx \
     asmcomp/stackframe.cmi
 endif # ifeq "$(ARCH)" "power"
 ifeq "$(ARCH)" "s390x"
@@ -8547,11 +8562,11 @@ debugger/debugger_config.cmx : \
     debugger/debugger_config.cmi
 debugger/debugger_config.cmi :
 debugger/debugger_lexer.cmo : \
-    utils/misc.cmi \
+    utils/utf8_lexeme.cmi \
     debugger/debugger_parser.cmi \
     debugger/debugger_lexer.cmi
 debugger/debugger_lexer.cmx : \
-    utils/misc.cmx \
+    utils/utf8_lexeme.cmx \
     debugger/debugger_parser.cmx \
     debugger/debugger_lexer.cmi
 debugger/debugger_lexer.cmi : \
@@ -9577,20 +9592,20 @@ ocamldoc/odoc_latex_style.cmx : \
     ocamldoc/odoc_latex_style.cmi
 ocamldoc/odoc_latex_style.cmi :
 ocamldoc/odoc_lexer.cmo : \
+    utils/utf8_lexeme.cmi \
     otherlibs/str/str.cmi \
     ocamldoc/odoc_parser.cmi \
     ocamldoc/odoc_messages.cmi \
     ocamldoc/odoc_global.cmi \
     ocamldoc/odoc_comments_global.cmi \
-    utils/misc.cmi \
     ocamldoc/odoc_lexer.cmi
 ocamldoc/odoc_lexer.cmx : \
+    utils/utf8_lexeme.cmx \
     otherlibs/str/str.cmx \
     ocamldoc/odoc_parser.cmx \
     ocamldoc/odoc_messages.cmx \
     ocamldoc/odoc_global.cmx \
     ocamldoc/odoc_comments_global.cmx \
-    utils/misc.cmx \
     ocamldoc/odoc_lexer.cmi
 ocamldoc/odoc_lexer.cmi : \
     ocamldoc/odoc_parser.cmi
@@ -9732,12 +9747,12 @@ ocamldoc/odoc_name.cmi : \
     parsing/longident.cmi \
     typing/ident.cmi
 ocamldoc/odoc_ocamlhtml.cmo : \
+    utils/utf8_lexeme.cmi \
     otherlibs/str/str.cmi \
-    utils/misc.cmi \
     ocamldoc/odoc_ocamlhtml.cmi
 ocamldoc/odoc_ocamlhtml.cmx : \
+    utils/utf8_lexeme.cmx \
     otherlibs/str/str.cmx \
-    utils/misc.cmx \
     ocamldoc/odoc_ocamlhtml.cmi
 ocamldoc/odoc_ocamlhtml.cmi :
 ocamldoc/odoc_parameter.cmo : \

.gitattributes

@@ -122,11 +122,12 @@ otherlibs/unix/stat_win32.c        typo.long-line
 otherlibs/unix/symlink_win32.c     typo.long-line
 
 # Some Unicode characters here and there
-utils/misc.ml            typo.non-ascii
+utils/utf8_lexeme.ml     typo.non-ascii
 runtime/sak.c            typo.non-ascii
 tools/opam/process.sh    typo.non-ascii
 
 testsuite/tests/**                                      typo.missing-header typo.long-line=may
+testsuite/tests/basic-manyargs/outgoing_stack_args_.c   typo.missing-header=false
 testsuite/tests/lib-bigarray-2/bigarrf.f                typo.tab linguist-language=Fortran
 testsuite/tests/lib-unix/win-stat/fakeclock.c           typo.missing-header=false
 testsuite/tests/misc-unsafe/almabench.ml                typo.long-line

.github/ISSUE_TEMPLATE/bug_report.md

@@ -12,6 +12,8 @@ Welcome to OCaml's Issue tracker!
 OCaml's developers use this tracker for bugs and feature requests only, rather
 than user support.
 
+**Note**: please do not include AI-generated text in your issue description or further comments. For more details, see our [guidelines relevant to AI-assisted bug reports](https://github.com/ocaml/ocaml/blob/trunk/AI.md#guidelines-relevant-to-ai-assisted-bug-reports).
+
 If you have questions about *using* OCaml, please ask at
 https://discuss.ocaml.org (more people read Discuss than this tracker, and
 you'll get confirmation of whether you've really found a bug or need a new

.github/workflows/build-cross.yml

@@ -277,6 +277,11 @@ jobs:
           cat example.ml
           $HOME/cross/bin/ocamlopt.opt example.ml -o example -verbose
           file example
+      - name: Enable KVM group perms
+        run: |
+          echo 'KERNEL=="kvm", GROUP="kvm", MODE="0666", OPTIONS+="static_node=kvm"' | sudo tee /etc/udev/rules.d/99-kvm4all.rules
+          sudo udevadm control --reload-rules
+          sudo udevadm trigger --name-match=kvm
       - name: Run example
         uses: reactivecircus/android-emulator-runner@v2
         with:

.github/workflows/hygiene.yml

@@ -18,7 +18,7 @@ concurrency:
 jobs:
   hygiene:
     name: Checks
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-26.04
     steps:
       - name: GitHub Context
         run: echo $GITHUB_CONTEXT

AI.md

@@ -29,3 +29,30 @@ a direct counterpart, with entirely human-produced content.
    of code that contributors do not understand; plagiarised works; hallucinated
    security reports; or experiments involving humans without their advance
    consent.
+
+## Guidelines relevant to AI-assisted bug reports
+
+Our advice is to avoid adding LLM-generated contents or explanations to
+your initial bug report: a bug report should be to the point and
+contain only human-verified information. Adding LLM-generated contents
+runs counter to those objectives, even if the generated contents
+looks useful to you.
+
+Indeed, judging the quality of a LLM-generated content about an
+unknown code base requires a lot of effort. Simultaneously, estimating
+the faithfulness of LLM-generated contents without knowing your prior
+understanding of the code base, nor your prompt, nor the model context
+also requires a lot of effort. Such efforts are in most cases better
+spent investigating the bug itself.
+
+Moreover, mixing human and LLM-generated contents in the same report
+without a clear separation should be imperatively avoided. Indeed,
+the absence of a clear delineation between the two contents makes it
+very hard to ascertain the reliability of any part of the mixed
+contents.
+
+We also advise some caution when shrinking reproduction case with
+LLMs. If you have any doubts about the LLM-shrinked reproduction case,
+please report both the original reproduction case and the shrinked
+one. In extreme cases, we have witnessed LLMs convincing people to
+reduce their bug report to a hallucination.

CONTRIBUTING.md

@@ -7,21 +7,15 @@ OCaml distribution. These are just guidelines, not rules, use your
 best judgment and feel free to propose changes to this document itself
 in a pull request.
 
-This document assumes that you have a patch against the sources of the
-compiler distribution, that you wish to submit to the OCaml
-maintainers upstream. See [INSTALL.adoc](INSTALL.adoc) for details on
-how to build the compiler distribution from sources. See
-[HACKING.adoc](HACKING.adoc) for details on how to modify the sources.
-
 ## Contribution
 
 Modifying the sources is far from the only way to contribute to the
-OCaml distribution. Bug reports (in particular when they come with
-a reproducible example), simple typos or clarifications in the
-documentation also help, and help evaluating and integrating existing
-change proposals also helps. Providing good answers on the discussion
-forums, or asking the good questions that highlight deficiencies in
-existing documentations, also help.
+OCaml distribution. Other contributions include:
+- Bug reports (in particular when they come with a reproducible example).
+- Simple typos or clarifications in the documentation
+- Help evaluating and integrating existing change proposals.
+- Providing good answers on the discussion forums
+- Asking questions that highlight deficiencies in existing documentations.
 
 There are also many valuable ways to contribute to the wider OCaml
 ecosystem that do not involve changes to the OCaml distribution.
@@ -31,6 +25,13 @@ proposals against the OCaml distribution. (Code changes, but also
 improvement to documentation or implementation comments, which are
 valuable changes on their own.)
 
+This document assumes that you have a patch against the sources of the
+compiler distribution or an idea for such a patch.
+
+This document is concerned with the process of getting your work merged
+upstream. For advice on how to build the compiler from sources
+see [INSTALL.adoc](INSTALL.adoc) and [HACKING.adoc](HACKING.adoc) instead.
+
 ## Workflow
 
 All changes to the OCaml distribution need to be processed through the
@@ -84,6 +85,7 @@ The current list of maintainers is as follows:
 - @OlivierNicole Olivier Nicole
 - @sadiqj Sadiq Jaffer
 - @shindere Sébastien Hinderer
+- @smuenzel Stefan Muenzel
 - @stedolan Stephen Dolan
 - @trefis Thomas Refis
 - @xavierleroy Xavier Leroy
@@ -114,6 +116,25 @@ the PR or issue.
 
 For more information about when and how new releases are published, see [the release introduction](release-info/introduction.md).
 
+## Pull-Request guideline
+
+You should open a pull request as a way to discuss the changes you are
+proposing. In some cases, you can open a pull request which contains proposed
+changes directly. In other cases, you should first open a pull request on the
+https://github.com/ocaml/RFCs repository to discuss some aspects of your changes.
+
+Chose the pull request route if you have a mature implementation, if you have
+already discussed the changes in advance, if your changes are purely
+implementation details without wider implications, or some such situation.
+
+Chose the RFC route if you merely have a prototype, if you haven't discussed or
+iterated on your design much, if your changes may impact the ecosystem at large
+(the users, the libraries, the build systems, etc.). Basically, use the RFC route
+to get more feedback on the earlier stages of your work.
+
+The rest of this document is concerned only with the pull request route. For
+the RFC route, you can find some documentation on the RFC repository directly.
+
 ## Coding guidelines
 
 You should not leave trailing whitespace; not have line longer than 80