docs(unstable-book): Document const generics features by popzxc · Pull Request #155543 · rust-lang/rust

popzxc · 2026-04-20T06:55:41Z

Relevant tracking issues: #113521 #132980 #76560 #151972

What

Adds a high-level overview of 4 unstable features related to const generic exprs.

Why

While trying to learn about the current state of const generic exprs, I found it a bit too hard due to lack of documentation -- had to read through a bunch of tracking issues & look for PRs/examples in the repo just to understand what the feature is about.

Moreover, given that there is a bunch of features with similarly-looking names, it was even more confusing. For that purpose, I also added cross-referencing across (directly or logically) related features.

As a result, I decided to add some more context to the unstable book, so that new readers have an easier time than I had.

Caveats

I understand that the features are incomplete/experimental, so the docs are at risk of becoming stale, but the book entrypoint already has a corresponding warning, so I guess it should be fine.

Also, given that I did research myself, the examples provided might be not the best to showcase the feature -- happy to provide better examples, if you have suggestions. The examples provided are what "made the feature make sense" to me as an outsider, so there is a chance that they will be good for other external readers too, though.

LLM use disclosue: an LLM was used for self-review only; research, coming up with examples, and writing is mine. Issues reported by LLM were fixed manually too.

r? @BoxyUwU

rustbot · 2026-04-20T06:55:47Z

BoxyUwU is currently at their maximum review capacity.
They may take a while to respond.

popzxc

Some comments to assist with the review.

View changes since this review

popzxc · 2026-04-20T06:59:59Z

+    let mut i = 0;
+    while i < B::Y {
+        let mut j = 0;
+        while j < B::X {
+            out[i * B::X + j] = y[i].saturating_mul(x[j]);
+            j += 1;
+        }
+        i += 1;
+    }


This body sort of shifts the attention from the things I wanted to highlight, but I thought that adding todo!() here would not feel genuine for readers.

popzxc · 2026-04-20T07:01:28Z

@@ -0,0 +1,59 @@
+# generic_const_items


Not directly related to other 3, but it 1. seems to be cross-referenced a lot (e.g. in UI tests), and 2. similar in spirit and might often be a thing that people actually want to have.

popzxc · 2026-04-20T07:03:15Z

@@ -0,0 +1,110 @@
+# min_generic_const_args
+
+Enables the generic const args MVP.


The feature description also states (only bare paths, not arbitrary computation), which feels out of date now -- right now more functionality seems to be supported, but I did not change any rust source code, as this feature is only about the documentation. Happy to change to whatever phrasing works better, both here and in unstable.rs if required.

right now the things mGCA supports are:

paths to type const items (e.g. ::ASSOC)

tuple constructor calls (e.g. Some(N)

struct/enum variant expressions (e.g. Some { 0: N })

paths to const constructors (e.g. None::)

tuple expressions (e.g. (N,))

array expressions (e.g. [N, N])

maybe concise wording here is "Paths to type const items and constructors for ADTs and primitives"

popzxc · 2026-04-20T07:04:05Z

@@ -0,0 +1,72 @@
+# generic_const_exprs
+
+Allows non-trivial generic constants which have to have wfness manually propagated to callers


"wfness" might be an unfamiliar term for people outside of Rust compiler developers community, so it might not be suitable for public documentation; left it here because it's technically correct and used in unstable.rs.

wfness = well-formedness; I would at least use the written-out form since that's an established term in linguistics that's searchable.

I would say something like "which have to be shown to successfully evaluate to a value by being part of an item signature". i think even the fully written "well-formedness" is a bit too jargon

BoxyUwU · 2026-04-20T11:47:22Z

+
+Related features: [generic_const_args], [generic_const_items].
+
+[feature_background]: https://hackmd.io/OsVAAEgOS2ajDwxg44kN-A?view


I think linking to a hackmd file is somewhat unfortunate 🤔 would you be willing to make a PR to the rust-lang/project-const-generics repo adding a documents/ directory and moving this document into there?

then we can link to a markdown file on github instead of a hackmd link

View changes since the review

Yup, will do slightly later!

…_const_exprs)

popzxc · 2026-04-20T14:52:35Z

+
+Related features: [generic_const_args], [generic_const_items].
+
+[feature_background]: https://github.com/rust-lang/project-const-generics/blob/main/documents/min_const_generics_plan.md


Link updated, pending corresponding PR merge

View changes since the review

Co-authored-by: León Orell Valerian Liehr <me@fmease.dev>

popzxc · 2026-04-28T17:14:21Z

@BoxyUwU is there anything else that needs to be done either in rust-lang/project-const-generics#110 or this PR?

BoxyUwU · 2026-05-01T10:36:34Z

left a comment on the other PR, this should be good to go once that's merged :)

BoxyUwU · 2026-05-01T10:36:58Z

@rustbot author

rustbot · 2026-05-01T10:37:02Z

Reminder, once the PR becomes ready for a review, use @rustbot ready.

popzxc · 2026-05-04T08:05:40Z

@rustbot ready

This PR links the markdown file and the PR is merged, so should be good to go.
Also opened rust-lang/project-const-generics#112 to fix the book deployment.

BoxyUwU · 2026-05-04T12:37:35Z

@bors r+ rollup

rust-bors · 2026-05-04T12:37:37Z

📌 Commit c4eb1bf has been approved by BoxyUwU

It is now in the queue for this repository.

@BoxyUwU

…ures, r=BoxyUwU docs(unstable-book): Document const generics features Relevant tracking issues: rust-lang#113521 rust-lang#132980 rust-lang#76560 rust-lang#151972 ## What Adds a high-level overview of 4 unstable features related to const generic exprs. ## Why While trying to learn about the current state of const generic exprs, I found it a bit too hard due to lack of documentation -- had to read through a bunch of tracking issues & look for PRs/examples in the repo just to understand what the feature is about. Moreover, given that there is a bunch of features with similarly-looking names, it was even more confusing. For that purpose, I also added cross-referencing across (directly or logically) related features. As a result, I decided to add some more context to the unstable book, so that new readers have an easier time than I had. ## Caveats I understand that the features are incomplete/experimental, so the docs are at risk of becoming stale, but the book entrypoint already has [a corresponding warning](https://doc.rust-lang.org/unstable-book/), so I guess it should be fine. Also, given that I did research myself, the examples provided might be not the best to showcase the feature -- happy to provide better examples, if you have suggestions. The examples provided are what "made the feature make sense" to me as an outsider, so there is a chance that they will be good for other external readers too, though. LLM use disclosue: an LLM was used for self-review only; research, coming up with examples, and writing is mine. Issues reported by LLM were fixed manually too. r? @BoxyUwU

rust-bors · 2026-05-04T12:42:23Z

⌛ Testing commit c4eb1bf with merge 1fac9f8...

Workflow: https://github.com/rust-lang/rust/actions/runs/25319609277

@BoxyUwU

…yUwU docs(unstable-book): Document const generics features Relevant tracking issues: #113521 #132980 #76560 #151972 ## What Adds a high-level overview of 4 unstable features related to const generic exprs. ## Why While trying to learn about the current state of const generic exprs, I found it a bit too hard due to lack of documentation -- had to read through a bunch of tracking issues & look for PRs/examples in the repo just to understand what the feature is about. Moreover, given that there is a bunch of features with similarly-looking names, it was even more confusing. For that purpose, I also added cross-referencing across (directly or logically) related features. As a result, I decided to add some more context to the unstable book, so that new readers have an easier time than I had. ## Caveats I understand that the features are incomplete/experimental, so the docs are at risk of becoming stale, but the book entrypoint already has [a corresponding warning](https://doc.rust-lang.org/unstable-book/), so I guess it should be fine. Also, given that I did research myself, the examples provided might be not the best to showcase the feature -- happy to provide better examples, if you have suggestions. The examples provided are what "made the feature make sense" to me as an outsider, so there is a chance that they will be good for other external readers too, though. LLM use disclosue: an LLM was used for self-review only; research, coming up with examples, and writing is mine. Issues reported by LLM were fixed manually too. r? @BoxyUwU

jhpratt · 2026-05-04T12:43:19Z

@bors yield

For encompassing rollup

rust-bors · 2026-05-04T12:43:24Z

Auto build was cancelled. Cancelled workflows:

https://github.com/rust-lang/rust/actions/runs/25319609277

The next pull request likely to be tested is #156140.

Rollup of 6 pull requests Successful merges: - #155543 (docs(unstable-book): Document const generics features) - #156043 (c-variadic: gate `va_arg` on `c_variadic_experimental_arch`) - #156082 (Move tests associated types) - #156092 (Clean up `TyCtxt::needs_crate_hash` usage and rename it to `needs_hir_hash`.) - #156104 (Relax `T: Sized` bound on `try_as_dyn` / `try_as_dyn_mut`) - #156128 (.mailmap: prefer matching just based on commit emails)

@BoxyUwU

…ures, r=BoxyUwU docs(unstable-book): Document const generics features Relevant tracking issues: rust-lang#113521 rust-lang#132980 rust-lang#76560 rust-lang#151972 ## What Adds a high-level overview of 4 unstable features related to const generic exprs. ## Why While trying to learn about the current state of const generic exprs, I found it a bit too hard due to lack of documentation -- had to read through a bunch of tracking issues & look for PRs/examples in the repo just to understand what the feature is about. Moreover, given that there is a bunch of features with similarly-looking names, it was even more confusing. For that purpose, I also added cross-referencing across (directly or logically) related features. As a result, I decided to add some more context to the unstable book, so that new readers have an easier time than I had. ## Caveats I understand that the features are incomplete/experimental, so the docs are at risk of becoming stale, but the book entrypoint already has [a corresponding warning](https://doc.rust-lang.org/unstable-book/), so I guess it should be fine. Also, given that I did research myself, the examples provided might be not the best to showcase the feature -- happy to provide better examples, if you have suggestions. The examples provided are what "made the feature make sense" to me as an outsider, so there is a chance that they will be good for other external readers too, though. LLM use disclosue: an LLM was used for self-review only; research, coming up with examples, and writing is mine. Issues reported by LLM were fixed manually too. r? @BoxyUwU

@BoxyUwU

…ures, r=BoxyUwU docs(unstable-book): Document const generics features Relevant tracking issues: rust-lang#113521 rust-lang#132980 rust-lang#76560 rust-lang#151972 ## What Adds a high-level overview of 4 unstable features related to const generic exprs. ## Why While trying to learn about the current state of const generic exprs, I found it a bit too hard due to lack of documentation -- had to read through a bunch of tracking issues & look for PRs/examples in the repo just to understand what the feature is about. Moreover, given that there is a bunch of features with similarly-looking names, it was even more confusing. For that purpose, I also added cross-referencing across (directly or logically) related features. As a result, I decided to add some more context to the unstable book, so that new readers have an easier time than I had. ## Caveats I understand that the features are incomplete/experimental, so the docs are at risk of becoming stale, but the book entrypoint already has [a corresponding warning](https://doc.rust-lang.org/unstable-book/), so I guess it should be fine. Also, given that I did research myself, the examples provided might be not the best to showcase the feature -- happy to provide better examples, if you have suggestions. The examples provided are what "made the feature make sense" to me as an outsider, so there is a chance that they will be good for other external readers too, though. LLM use disclosue: an LLM was used for self-review only; research, coming up with examples, and writing is mine. Issues reported by LLM were fixed manually too. r? @BoxyUwU

…uwer Rollup of 10 pull requests Successful merges: - #155848 ([doc]: Revert `core::io::ErrorKind` doc changes) - #155855 (Remove unnecessary `get_unchecked`) - #156062 (Added command-line argument support for `wasm32-wali-linux-musl`) - #155543 (docs(unstable-book): Document const generics features) - #156043 (c-variadic: gate `va_arg` on `c_variadic_experimental_arch`) - #156082 (Move tests associated types) - #156092 (Clean up `TyCtxt::needs_crate_hash` usage and rename it to `needs_hir_hash`.) - #156104 (Relax `T: Sized` bound on `try_as_dyn` / `try_as_dyn_mut`) - #156128 (.mailmap: prefer matching just based on commit emails) - #156135 (Remove most uses of def_id_to_node_id)

@BoxyUwU

…ures, r=BoxyUwU docs(unstable-book): Document const generics features Relevant tracking issues: rust-lang#113521 rust-lang#132980 rust-lang#76560 rust-lang#151972 ## What Adds a high-level overview of 4 unstable features related to const generic exprs. ## Why While trying to learn about the current state of const generic exprs, I found it a bit too hard due to lack of documentation -- had to read through a bunch of tracking issues & look for PRs/examples in the repo just to understand what the feature is about. Moreover, given that there is a bunch of features with similarly-looking names, it was even more confusing. For that purpose, I also added cross-referencing across (directly or logically) related features. As a result, I decided to add some more context to the unstable book, so that new readers have an easier time than I had. ## Caveats I understand that the features are incomplete/experimental, so the docs are at risk of becoming stale, but the book entrypoint already has [a corresponding warning](https://doc.rust-lang.org/unstable-book/), so I guess it should be fine. Also, given that I did research myself, the examples provided might be not the best to showcase the feature -- happy to provide better examples, if you have suggestions. The examples provided are what "made the feature make sense" to me as an outsider, so there is a chance that they will be good for other external readers too, though. LLM use disclosue: an LLM was used for self-review only; research, coming up with examples, and writing is mine. Issues reported by LLM were fixed manually too. r? @BoxyUwU

…uwer Rollup of 10 pull requests Successful merges: - #155848 ([doc]: Revert `core::io::ErrorKind` doc changes) - #155855 (Remove unnecessary `get_unchecked`) - #155543 (docs(unstable-book): Document const generics features) - #155962 (`rustc`: `target_features`: allow for `cfg`-only stable `target_features`) - #156043 (c-variadic: gate `va_arg` on `c_variadic_experimental_arch`) - #156082 (Move tests associated types) - #156092 (Clean up `TyCtxt::needs_crate_hash` usage and rename it to `needs_hir_hash`.) - #156104 (Relax `T: Sized` bound on `try_as_dyn` / `try_as_dyn_mut`) - #156128 (.mailmap: prefer matching just based on commit emails) - #156135 (Remove most uses of def_id_to_node_id)

@BoxyUwU

…ures, r=BoxyUwU docs(unstable-book): Document const generics features Relevant tracking issues: rust-lang#113521 rust-lang#132980 rust-lang#76560 rust-lang#151972 ## What Adds a high-level overview of 4 unstable features related to const generic exprs. ## Why While trying to learn about the current state of const generic exprs, I found it a bit too hard due to lack of documentation -- had to read through a bunch of tracking issues & look for PRs/examples in the repo just to understand what the feature is about. Moreover, given that there is a bunch of features with similarly-looking names, it was even more confusing. For that purpose, I also added cross-referencing across (directly or logically) related features. As a result, I decided to add some more context to the unstable book, so that new readers have an easier time than I had. ## Caveats I understand that the features are incomplete/experimental, so the docs are at risk of becoming stale, but the book entrypoint already has [a corresponding warning](https://doc.rust-lang.org/unstable-book/), so I guess it should be fine. Also, given that I did research myself, the examples provided might be not the best to showcase the feature -- happy to provide better examples, if you have suggestions. The examples provided are what "made the feature make sense" to me as an outsider, so there is a chance that they will be good for other external readers too, though. LLM use disclosue: an LLM was used for self-review only; research, coming up with examples, and writing is mine. Issues reported by LLM were fixed manually too. r? @BoxyUwU

…uwer Rollup of 12 pull requests Successful merges: - #155848 ([doc]: Revert `core::io::ErrorKind` doc changes) - #155855 (Remove unnecessary `get_unchecked`) - #155543 (docs(unstable-book): Document const generics features) - #155962 (`rustc`: `target_features`: allow for `cfg`-only stable `target_features`) - #156043 (c-variadic: gate `va_arg` on `c_variadic_experimental_arch`) - #156082 (Move tests associated types) - #156092 (Clean up `TyCtxt::needs_crate_hash` usage and rename it to `needs_hir_hash`.) - #156103 (Fix E0040 suggestion for explicit `Drop::drop` UFCS calls) - #156104 (Relax `T: Sized` bound on `try_as_dyn` / `try_as_dyn_mut`) - #156128 (.mailmap: prefer matching just based on commit emails) - #156135 (Remove most uses of def_id_to_node_id) - #156152 (Update books)

@BoxyUwU

…ures, r=BoxyUwU docs(unstable-book): Document const generics features Relevant tracking issues: rust-lang#113521 rust-lang#132980 rust-lang#76560 rust-lang#151972 ## What Adds a high-level overview of 4 unstable features related to const generic exprs. ## Why While trying to learn about the current state of const generic exprs, I found it a bit too hard due to lack of documentation -- had to read through a bunch of tracking issues & look for PRs/examples in the repo just to understand what the feature is about. Moreover, given that there is a bunch of features with similarly-looking names, it was even more confusing. For that purpose, I also added cross-referencing across (directly or logically) related features. As a result, I decided to add some more context to the unstable book, so that new readers have an easier time than I had. ## Caveats I understand that the features are incomplete/experimental, so the docs are at risk of becoming stale, but the book entrypoint already has [a corresponding warning](https://doc.rust-lang.org/unstable-book/), so I guess it should be fine. Also, given that I did research myself, the examples provided might be not the best to showcase the feature -- happy to provide better examples, if you have suggestions. The examples provided are what "made the feature make sense" to me as an outsider, so there is a chance that they will be good for other external readers too, though. LLM use disclosue: an LLM was used for self-review only; research, coming up with examples, and writing is mine. Issues reported by LLM were fixed manually too. r? @BoxyUwU

Rollup of 16 pull requests Successful merges: - #155848 ([doc]: Revert `core::io::ErrorKind` doc changes) - #155855 (Remove unnecessary `get_unchecked`) - #155543 (docs(unstable-book): Document const generics features) - #155962 (`rustc`: `target_features`: allow for `cfg`-only stable `target_features`) - #156043 (c-variadic: gate `va_arg` on `c_variadic_experimental_arch`) - #156082 (Move tests associated types) - #156087 (Improve `&pin` reference-pattern suggestions) - #156092 (Clean up `TyCtxt::needs_crate_hash` usage and rename it to `needs_hir_hash`.) - #156103 (Fix E0040 suggestion for explicit `Drop::drop` UFCS calls) - #156104 (Relax `T: Sized` bound on `try_as_dyn` / `try_as_dyn_mut`) - #156122 (Add a `doc_cfg` regression test to ensure foreign types impls are working as expected) - #156128 (.mailmap: prefer matching just based on commit emails) - #156135 (Remove most uses of def_id_to_node_id) - #156152 (Update books) - #156154 (tests: mark import UI tests as check-pass) - #156162 (Update `browser-ui-test` version to `0.23.5`)

rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Apr 20, 2026

rustbot assigned BoxyUwU Apr 20, 2026

popzxc commented Apr 20, 2026

View reviewed changes

This comment has been minimized.

Sign in to view

popzxc force-pushed the document-generic-const-features branch from 59f05a0 to b4886b2 Compare April 20, 2026 08:14

BoxyUwU reviewed Apr 20, 2026

View reviewed changes

popzxc mentioned this pull request Apr 20, 2026

Migrate min_const_generics_plan from hack.md rust-lang/project-const-generics#110

Merged

popzxc added 3 commits April 20, 2026 18:13

docs(unstable-book): Document const generics features

5eae716

Update unstable feature descriptions (min_generic_const_args, generic…

6315e17

…_const_exprs)

Change generic_const_args feature from unstable to incomplete

73e44e8

popzxc force-pushed the document-generic-const-features branch from b4886b2 to 73e44e8 Compare April 20, 2026 14:51

rustbot added the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Apr 20, 2026

popzxc commented Apr 20, 2026

View reviewed changes

fmease reviewed Apr 22, 2026

View reviewed changes

Comment thread src/doc/unstable-book/src/language-features/generic-const-items.md Outdated

Comment thread src/doc/unstable-book/src/language-features/generic-const-items.md Outdated

This comment has been minimized.

Sign in to view

Do not use const { } blocks for GCI

c4eb1bf

Co-authored-by: León Orell Valerian Liehr <me@fmease.dev>

popzxc force-pushed the document-generic-const-features branch from 656bb20 to c4eb1bf Compare April 23, 2026 05:08

rustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels May 1, 2026

rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels May 4, 2026

rust-bors Bot added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label May 4, 2026

rust-bors Bot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label May 4, 2026

jhpratt mentioned this pull request May 4, 2026

Rollup of 6 pull requests #156140

Closed

JonathanBrouwer mentioned this pull request May 4, 2026

Rollup of 9 pull requests #156149

Closed

JonathanBrouwer mentioned this pull request May 4, 2026

Rollup of 10 pull requests #156150

Closed

JonathanBrouwer mentioned this pull request May 4, 2026

Rollup of 10 pull requests #156153

Closed

JonathanBrouwer mentioned this pull request May 4, 2026

Rollup of 12 pull requests #156158

Open

GuillaumeGomez mentioned this pull request May 5, 2026

Rollup of 16 pull requests #156166

Open

		@@ -0,0 +1,110 @@
		# min_generic_const_args

		Enables the generic const args MVP.

		@@ -0,0 +1,72 @@
		# generic_const_exprs

		Allows non-trivial generic constants which have to have wfness manually propagated to callers


		Related features: [generic_const_args], [generic_const_items].

		[feature_background]: https://hackmd.io/OsVAAEgOS2ajDwxg44kN-A?view


		Related features: [generic_const_args], [generic_const_items].

		[feature_background]: https://github.com/rust-lang/project-const-generics/blob/main/documents/min_const_generics_plan.md

Uh oh!

Conversation

popzxc commented Apr 20, 2026 • edited by rustbot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What

Why

Caveats

Uh oh!

rustbot commented Apr 20, 2026

Uh oh!

popzxc left a comment • edited by rustbot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

popzxc Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

popzxc Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

popzxc Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

BoxyUwU Apr 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

BoxyUwU Apr 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

popzxc Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

fmease Apr 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

BoxyUwU Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

This comment has been minimized.

BoxyUwU Apr 20, 2026 • edited by rustbot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

popzxc Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

popzxc Apr 20, 2026 • edited by rustbot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

This comment has been minimized.

popzxc commented Apr 28, 2026

Uh oh!

BoxyUwU commented May 1, 2026

Uh oh!

BoxyUwU commented May 1, 2026

Uh oh!

rustbot commented May 1, 2026

Uh oh!

popzxc commented May 4, 2026

Uh oh!

BoxyUwU commented May 4, 2026

Uh oh!

rust-bors Bot commented May 4, 2026

Uh oh!

rust-bors Bot commented May 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jhpratt commented May 4, 2026

Uh oh!

rust-bors Bot commented May 4, 2026

Uh oh!

Reviewers

popzxc commented Apr 20, 2026 •

edited by rustbot

Loading

popzxc left a comment •

edited by rustbot

Loading

BoxyUwU Apr 20, 2026 •

edited

Loading

BoxyUwU Apr 20, 2026 •

edited

Loading

fmease Apr 20, 2026 •

edited

Loading

BoxyUwU Apr 20, 2026 •

edited by rustbot

Loading

popzxc Apr 20, 2026 •

edited by rustbot

Loading

rust-bors Bot commented May 4, 2026 •

edited

Loading