[pull] master from rust-lang:master

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,34 @@
+---
+name: Bug report
+about: An issue with the current behavior of the regex crate.
+title: ''
+labels: ''
+assignees: ''
+---
+
+
+#### What version of regex are you using?
+
+If it isn't the latest version, then please upgrade and check whether the bug
+is still present.
+
+#### Describe the bug at a high level.
+
+Give a brief description of the actual problem you're observing.
+
+#### What are the steps to reproduce the behavior?
+
+This section should almost always provide a COMPLETE Rust program that others
+can compile and run with Cargo. It should be as small as possible.
+
+If providing a small and simple reproduction is not easy, please explain why
+and the maintainers will help you figure out next steps.
+
+#### What is the actual behavior?
+
+If you provide a Rust program in the previous section, then this should be the
+output of that program.
+
+#### What is the expected behavior?
+
+What do you expect the output to be?

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,7 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Ask a question
+    about: |
+      You've come to seek help or want to discuss something related to the
+      regex crate.
+    url: https://github.com/rust-lang/regex/discussions/new

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest a new feature
+title: ''
+labels: ''
+assignees: ''
+---
+
+
+#### Describe your feature request
+
+Please describe the behavior you want and the motivation. Please also provide
+examples of how the new feature would be used if your feature request were
+added.
+
+The best kind of feature request is one that proposes a concrete change to the
+API along with a sketch of the changes to the public API documentation.
+
+If you're not sure what to write here, then try imagining what the ideal
+documentation of your new feature would look like. Then try to write it.

.github/workflows/ci.yml

@@ -0,0 +1,240 @@
+name: ci
+on:
+  pull_request:
+  push:
+    branches:
+    - master
+  schedule:
+  - cron: '00 01 * * *'
+
+# The section is needed to drop write-all permissions that are granted on
+# `schedule` event. By specifying any permission explicitly all others are set
+# to none. By using the principle of least privilege the damage a compromised
+# workflow can do (because of an injection or compromised third party tool or
+# action) is restricted. Currently the worklow doesn't need any additional
+# permission except for pulling the code. Adding labels to issues, commenting
+# on pull-requests, etc. may need additional permissions:
+#
+# Syntax for this section:
+# https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions
+#
+# Reference for how to assign permissions on a job-by-job basis:
+# https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs
+#
+# Reference for available permissions that we can enable if needed:
+# https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token
+permissions:
+  # to fetch code (actions/checkout)
+  contents: read
+
+jobs:
+  # This job does our basic build+test for supported platforms.
+  test:
+    env:
+      # For some builds, we use cross to test on 32-bit and big-endian
+      # systems.
+      CARGO: cargo
+      # When CARGO is set to CROSS, TARGET is set to `--target matrix.target`.
+      # Note that we only use cross on Linux, so setting a target on a
+      # different OS will just use normal cargo.
+      TARGET:
+      # Bump this as appropriate. We pin to a version to make sure CI
+      # continues to work as cross releases in the past have broken things
+      # in subtle ways.
+      CROSS_VERSION: v0.2.5
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+        - build: stable
+          os: ubuntu-latest
+          rust: stable
+        - build: stable-32
+          os: ubuntu-latest
+          rust: stable
+          target: i686-unknown-linux-gnu
+        - build: stable-powerpc64
+          os: ubuntu-latest
+          rust: stable
+          target: powerpc64-unknown-linux-gnu
+        - build: stable-s390x
+          os: ubuntu-latest
+          rust: stable
+          target: s390x-unknown-linux-gnu
+        - build: beta
+          os: ubuntu-latest
+          rust: beta
+        - build: nightly
+          os: ubuntu-latest
+          rust: nightly
+        - build: macos
+          os: macos-latest
+          rust: stable
+        - build: win-msvc
+          os: windows-latest
+          rust: stable
+        - build: win-gnu
+          os: windows-latest
+          rust: stable-x86_64-gnu
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+    - name: Install Rust
+      uses: dtolnay/rust-toolchain@master
+      with:
+        toolchain: ${{ matrix.rust }}
+    - name: Install and configure Cross
+      if: matrix.os == 'ubuntu-latest' && matrix.target != ''
+      run: |
+        # In the past, new releases of 'cross' have broken CI. So for now, we
+        # pin it. We also use their pre-compiled binary releases because cross
+        # has over 100 dependencies and takes a bit to compile.
+        dir="$RUNNER_TEMP/cross-download"
+        mkdir "$dir"
+        echo "$dir" >> $GITHUB_PATH
+        cd "$dir"
+        curl -LO "https://github.com/cross-rs/cross/releases/download/$CROSS_VERSION/cross-x86_64-unknown-linux-musl.tar.gz"
+        tar xf cross-x86_64-unknown-linux-musl.tar.gz
+        echo "CARGO=cross" >> $GITHUB_ENV
+        echo "TARGET=--target ${{ matrix.target }}" >> $GITHUB_ENV
+    - name: Show command used for Cargo
+      run: |
+        echo "cargo command is: $CARGO"
+        echo "target flag is: $TARGET"
+    - name: Show CPU info for debugging
+      if: matrix.os == 'ubuntu-latest'
+      run: lscpu
+    - name: Basic build
+      run: ${{ env.CARGO }} build --verbose $TARGET
+    - name: Build docs
+      run: ${{ env.CARGO }} doc --verbose $TARGET
+    - name: Run subset of tests
+      run: ${{ env.CARGO }} test --verbose --test integration $TARGET
+    - name: Build regex-syntax docs
+      run: ${{ env.CARGO }} doc --verbose --manifest-path regex-syntax/Cargo.toml $TARGET
+    - name: Run subset of regex-syntax tests
+      run: ${{ env.CARGO }} test --verbose --manifest-path regex-syntax/Cargo.toml $TARGET
+    - name: Build regex-automata docs
+      run: ${{ env.CARGO }} doc --verbose --manifest-path regex-automata/Cargo.toml $TARGET
+    - name: Run subset of regex-automata tests
+      if: matrix.build != 'win-gnu'  # Just horrifically slow.
+      run: ${{ env.CARGO }} test --verbose --manifest-path regex-automata/Cargo.toml $TARGET
+    - name: Run regex-lite tests
+      run: ${{ env.CARGO }} test --verbose --manifest-path regex-lite/Cargo.toml $TARGET
+    - name: Run regex-cli tests
+      run: ${{ env.CARGO }} test --verbose --manifest-path regex-cli/Cargo.toml $TARGET
+
+  # This job runs a stripped down version of CI to test the MSRV. The specific
+  # reason for doing this is that the regex crate's dev-dependencies tend to
+  # evolve more quickly. There isn't as tight of a control on them because,
+  # well, they're only used in tests and their MSRV doesn't matter as much.
+  #
+  # It is a bit unfortunate that our MSRV test is basically just "build it"
+  # and pass if that works. But usually MSRV is broken by compilation problems
+  # and not runtime behavior. So this is in practice good enough.
+  msrv:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+    - name: Install Rust
+      uses: dtolnay/rust-toolchain@master
+      with:
+        toolchain: 1.65.0
+    - name: Basic build
+      run: cargo build --verbose
+    - name: Build docs
+      run: cargo doc --verbose
+
+  # This job runs many more tests for the regex crate proper. Basically,
+  # it repeats the same test suite for a bunch of different crate feature
+  # combinations. There are so many features that exhaustive testing isn't
+  # really possible, but we cover as much as is feasible.
+  #
+  # If there is a feature combo that should be tested but isn't, you'll want to
+  # add it to the appropriate 'test' script in this repo.
+  testfull-regex:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+    - name: Install Rust
+      uses: dtolnay/rust-toolchain@master
+      with:
+        toolchain: stable
+    - name: Run full test suite
+      run: ./test
+
+  # Same as above, but for regex-automata, which has even more crate features!
+  testfull-regex-automata:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+    - name: Install Rust
+      uses: dtolnay/rust-toolchain@master
+      with:
+        toolchain: stable
+    - name: Run full test suite
+      run: ./regex-automata/test
+
+  # Same as above, but for regex-syntax.
+  testfull-regex-syntax:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+    - name: Install Rust
+      uses: dtolnay/rust-toolchain@master
+      with:
+        toolchain: stable
+    - name: Run full test suite
+      run: ./regex-syntax/test
+
+  # Same as above, but for regex-capi.
+  testfull-regex-capi:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+    - name: Install Rust
+      uses: dtolnay/rust-toolchain@master
+      with:
+        toolchain: stable
+    - name: Run full test suite
+      run: ./regex-capi/test
+
+  # Runs miri on regex-automata's test suite. This doesn't quite cover
+  # everything. Many tests are disabled when building with miri because of
+  # how slow miri runs. But it still gives us decent coverage.
+  miri-regex-automata:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+    - name: Install Rust
+      uses: dtolnay/rust-toolchain@master
+      with:
+        # We use nightly here so that we can use miri I guess?
+        # It caught me by surprise that miri seems to only be
+        # available on nightly.
+        toolchain: nightly
+        components: miri
+    - name: Run full test suite
+      run: cargo miri test --manifest-path regex-automata/Cargo.toml
+
+  # Tests that everything is formatted correctly.
+  rustfmt:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+    - name: Install Rust
+      uses: dtolnay/rust-toolchain@master
+      with:
+        toolchain: stable
+        components: rustfmt
+    - name: Check formatting
+      run: |
+        cargo fmt --all -- --check

.vim/coc-settings.json

@@ -0,0 +1,6 @@
+{
+  "rust-analyzer.linkedProjects": [
+    "fuzz/Cargo.toml",
+    "Cargo.toml"
+  ]
+}