resolve: Preserve ambiguous glob reexports in crate metadata by petrochenkov · Pull Request #147984 · rust-lang/rust

petrochenkov · 2025-10-22T13:12:42Z

So in cross-crate scenarios they can work in the same way as in crate-local scenarios.

Resurrection of #114682.
One of unblocking steps for #145108.
Fixes #36837.

rustbot · 2025-10-22T13:12:47Z

rustbot has assigned @jdonszelmann.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

petrochenkov · 2025-10-22T13:13:01Z

@bors try

resolve: Preserve ambiguous glob reexports in crate metadata

petrochenkov · 2025-10-22T13:14:38Z

cc @LorrensP-2158466 @bvanjoi

rust-bors · 2025-10-22T15:32:03Z

☀️ Try build successful (CI)
Build commit: b4c5508 (b4c55082edd8dec08ce8af276d7054d9c4db20c4, parent: f5e2df741b4a9820a7579f0c8eccc951706a8782)

petrochenkov · 2025-10-22T15:33:22Z

@craterbot check

craterbot · 2025-10-22T15:33:47Z

👌 Experiment pr-147984 created and queued.
🤖 Automatically detected try build b4c5508
🔍 You can check out the queue and this experiment's details.

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

craterbot · 2025-10-22T15:34:03Z

🚧 Experiment pr-147984 is now running

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

craterbot · 2025-10-24T07:11:57Z

🎉 Experiment pr-147984 is completed!
📊 2312 regressed and 2 fixed (721923 total)
📊 1766 spurious results on the retry-regessed-list.txt, consider a retry¹ if this is a significant amount.
📰 Open the summary report.

⚠️ If you notice any spurious failure please add them to the denylist!
ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

re-run the experiment with crates=https://crater-reports.s3.amazonaws.com/pr-147984/retry-regressed-list.txt ↩

petrochenkov · 2025-10-24T12:28:34Z

That's a lot of breakage.
Mostly from dependencies, including various version of openssl that we've seen previously.
I'll demote this error to always be reported as a lint in cross-crate scenarios, and then rerun crater.

petrochenkov · 2025-10-24T12:58:17Z

@bors try

@craterbot run mode=check-only p=1 crates=https://crater-reports.s3.amazonaws.com/pr-147984/retry-regressed-list.txt

resolve: Preserve ambiguous glob reexports in crate metadata

rust-bors · 2025-10-24T15:17:26Z

☀️ Try build successful (CI)
Build commit: c6359cd (c6359cd3b4418e8472bae1a89c242796f2b86d56, parent: 75948c8bb3bd37f1e8ee20273a04edea4c1f84f8)

petrochenkov · 2025-10-24T15:24:38Z

@craterbot run mode=check-only p=1 crates=https://crater-reports.s3.amazonaws.com/pr-147984/retry-regressed-list.txt

craterbot · 2025-10-24T15:24:47Z

👌 Experiment pr-147984-1 created and queued.
🤖 Automatically detected try build c6359cd
🔍 You can check out the queue and this experiment's details.

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

bors · 2025-12-09T16:22:58Z

⌛ Testing commit 51780a5 with merge c61a3a4...

bors · 2025-12-09T19:36:15Z

☀️ Test successful - checks-actions
Approved by: yaahc
Pushing c61a3a4 to main...

github-actions · 2025-12-09T19:39:08Z

What is this?

This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing e2893f7 (parent) -> c61a3a4 (this PR)

Test differences

Show 52 test diffs

Stage 1

[ui] tests/ui/imports/ambiguous-glob-vs-expanded-extern.rs: [missing] -> pass (J1)

Stage 2

[ui] tests/ui/imports/ambiguous-glob-vs-expanded-extern.rs: [missing] -> pass (J0)

Additionally, 50 doctest diffs were found. These are ignored, as they are noisy.

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard c61a3a44d1a5bee35914cada6c788a05e0808f5b --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

pr-check-1: 1663.0s -> 2020.4s (+21.5%)
x86_64-gnu-llvm-20-2: 5110.6s -> 6097.8s (+19.3%)
x86_64-gnu-llvm-20: 2399.9s -> 2836.2s (+18.2%)
aarch64-apple: 9367.4s -> 10755.1s (+14.8%)
x86_64-gnu-tools: 3169.7s -> 3613.6s (+14.0%)
dist-apple-various: 4313.7s -> 4913.7s (+13.9%)
i686-gnu-nopt-1: 7405.3s -> 8424.0s (+13.8%)
x86_64-gnu-llvm-20-3: 5752.6s -> 6517.7s (+13.3%)
x86_64-gnu-gcc: 3003.9s -> 3400.4s (+13.2%)
aarch64-gnu-llvm-20-2: 2086.6s -> 2346.4s (+12.5%)

How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

rust-timer · 2025-12-09T20:17:51Z

Finished benchmarking commit (c61a3a4): comparison URL.

Overall result: ❌ regressions - please read the text below

Our benchmarks found a performance regression caused by this PR.
This might be an actual regression, but it can also be just noise.

Next Steps:

If the regression was expected or you think it can be justified,
please write a comment with sufficient written justification, and add
@rustbot label: +perf-regression-triaged to it, to mark the regression as triaged.
If you think that you know of a way to resolve the regression, try to create
a new PR with a fix for the regression.
If you do not understand the regression or you think that it is just noise,
you can ask the @rust-lang/wg-compiler-performance working group for help (members of this group
were already notified of this PR).

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

	mean	range	count
Regressions ❌ (primary)	0.3%	[0.1%, 0.5%]	24
Regressions ❌ (secondary)	0.3%	[0.2%, 0.7%]	13
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.1%	[-0.1%, -0.1%]	1
All ❌✅ (primary)	0.3%	[0.1%, 0.5%]	24

Max RSS (memory usage)

Results (secondary 2.9%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	4.9%	[4.5%, 5.2%]	2
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.9%	[-0.9%, -0.9%]	1
All ❌✅ (primary)	-	-	0

Cycles

Results (secondary -3.2%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-3.2%	[-3.2%, -3.2%]	1
All ❌✅ (primary)	-	-	0

Binary size

Results (primary 0.2%, secondary 0.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	0.2%	[0.2%, 0.2%]	8
Regressions ❌ (secondary)	0.0%	[0.0%, 0.0%]	1
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.2%	[0.2%, 0.2%]	8

Bootstrap: 471.528s -> 471.772s (0.05%)
Artifact size: 388.98 MiB -> 389.00 MiB (0.00%)

Kobzol · 2025-12-16T08:17:09Z

Do you think there's something to be done about the regression? Seems like we are fundamentally doing more work here..

petrochenkov · 2025-12-16T09:57:25Z

Yes, we are doing more work when there are ambiguous reexports.
diesel-2.2.10 in particular is known to have a lot of them.
tt-muncher is probably noise, it's often noisy, but perf-rlo seems to be partially down, I can't see the Detailed results.
The other regressions are tiny, not sure if any of them have ambiguous reexports.

petrochenkov · 2025-12-16T13:49:57Z

cc @Razaekel
Together with diesel noise-0.7.0 is the largest source of ambiguous reexports here (it's also the largest source of regressions in #149195).
If you are willing to release a 0.7.1 version with a fix, then I will prepare a pull request.

The error typically looks like this.

error: `Perlin` is ambiguous
 --> src/terrain.rs:2:22
  |
2 | use noise::{NoiseFn, Perlin, Seedable};
  |                      ^^^^^^ ambiguous name
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
  = note: for more information, see issue #114095 <https://github.com/rust-lang/rust/issues/114095>
  = note: ambiguous because of multiple glob imports of a name in the same module
note: `Perlin` could refer to the struct defined here
 --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/noise-0.7.0/src/noise_fns/generators.rs:6:9
  |
6 | pub use self::perlin::*;
  |         ^^^^^^^^^^^^
note: `Perlin` could also refer to the struct defined here
 --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/noise-0.7.0/src/noise_fns/generators.rs:7:9
  |
7 | pub use self::perlin_surflet::*;
  |         ^^^^^^^^^^^^^^^^^^^^
  = note: `#[deny(ambiguous_glob_imports)]` (part of `#[deny(future_incompatible)]`) on by default

resolve: Mark items under exported ambiguous imports as exported After rust-lang#147984 one of the imports in an ambiguous import set becomes accessible under a deny-by-default deprecation lint. So if it points to something, that something needs to be marked as exported, so its MIR is encoded into metadata, its symbol is not lost from object files, etc. The added test shows an example. This fixes around 10-20 crater regressions found in rust-lang#149195 (comment). Unblocks rust-lang#149195.

resolve: Mark items under exported ambiguous imports as exported After #147984 one of the imports in an ambiguous import set becomes accessible under a deny-by-default deprecation lint. So if it points to something, that something needs to be marked as exported, so its MIR is encoded into metadata, its symbol is not lost from object files, etc. The added test shows an example. This fixes around 10-20 crater regressions found in #149195 (comment). Unblocks #149195.

resolve: Mark items under exported ambiguous imports as exported After rust-lang#147984 one of the imports in an ambiguous import set becomes accessible under a deny-by-default deprecation lint. So if it points to something, that something needs to be marked as exported, so its MIR is encoded into metadata, its symbol is not lost from object files, etc. The added test shows an example. This fixes around 10-20 crater regressions found in rust-lang#149195 (comment). Unblocks rust-lang#149195.

resolve: Mark items under exported ambiguous imports as exported After #147984 one of the imports in an ambiguous import set becomes accessible under a deny-by-default deprecation lint. So if it points to something, that something needs to be marked as exported, so its MIR is encoded into metadata, its symbol is not lost from object files, etc. The added test shows an example. This fixes around 10-20 crater regressions found in #149195 (comment). Unblocks #149195.

resolve: Mark items under exported ambiguous imports as exported After rust-lang#147984 one of the imports in an ambiguous import set becomes accessible under a deny-by-default deprecation lint. So if it points to something, that something needs to be marked as exported, so its MIR is encoded into metadata, its symbol is not lost from object files, etc. The added test shows an example. This fixes around 10-20 crater regressions found in rust-lang#149195 (comment). Unblocks rust-lang#149195.

resolve: Mark items under exported ambiguous imports as exported After rust-lang/rust#147984 one of the imports in an ambiguous import set becomes accessible under a deny-by-default deprecation lint. So if it points to something, that something needs to be marked as exported, so its MIR is encoded into metadata, its symbol is not lost from object files, etc. The added test shows an example. This fixes around 10-20 crater regressions found in rust-lang/rust#149195 (comment). Unblocks rust-lang/rust#149195.

Pkgsrc changes: * Update version & checksums. * Adapt patches to new vendored crates. This has so far just been verified to build on NetBSD/amd64. Upstream changes relative to 1.93.1: Version 1.94.0 (2026-03-05) ========================== Language -------- - [Impls and impl items inherit `dead_code` lint level of the corresponding traits and trait items] (rust-lang/rust#144113) - [Stabilize additional 29 RISC-V target features including large portions of the RVA22U64 / RVA23U64 profiles] (rust-lang/rust#145948) - [Add warn-by-default `unused_visibilities` lint for visibility on `const _` declarations] (rust-lang/rust#147136) - [Update to Unicode 17] (rust-lang/rust#148321) - [Avoid incorrect lifetime errors for closures] (rust-lang/rust#148329) Platform Support ---------------- - [Add `riscv64im-unknown-none-elf` as a tier 3 target] (rust-lang/rust#148790) Refer to Rust's [platform support page][platform-support-doc] for more information on Rust's tiered platform support. [platform-support-doc]: https://doc.rust-lang.org/rustc/platform-support.html Libraries --------- - [Relax `T: Ord` bound for some `BinaryHeap<T>` methods.] (rust-lang/rust#149408) Stabilized APIs --------------- - [`<[T]>::array_windows`] (https://doc.rust-lang.org/stable/std/primitive.slice.html#method.array_windows) - [`<[T]>::element_offset`] (https://doc.rust-lang.org/stable/std/primitive.slice.html#method.element_offset) - [`LazyCell::get`] (https://doc.rust-lang.org/stable/std/cell/struct.LazyCell.html#method.get) - [`LazyCell::get_mut`] (https://doc.rust-lang.org/stable/std/cell/struct.LazyCell.html#method.get_mut) - [`LazyCell::force_mut`] (https://doc.rust-lang.org/stable/std/cell/struct.LazyCell.html#method.force_mut) - [`LazyLock::get`] (https://doc.rust-lang.org/stable/std/sync/struct.LazyLock.html#method.get) - [`LazyLock::get_mut`] (https://doc.rust-lang.org/stable/std/sync/struct.LazyLock.html#method.get_mut) - [`LazyLock::force_mut`] (https://doc.rust-lang.org/stable/std/sync/struct.LazyLock.html#method.force_mut) - [`impl TryFrom<char> for usize`] (https://doc.rust-lang.org/stable/std/convert/trait.TryFrom.html#impl-TryFrom%3Cchar%3E-for-usize) - [`std::iter::Peekable::next_if_map`] (https://doc.rust-lang.org/stable/std/iter/struct.Peekable.html#method.next_if_map) - [`std::iter::Peekable::next_if_map_mut`] (https://doc.rust-lang.org/stable/std/iter/struct.Peekable.html#method.next_if_map_mut) - [x86 `avx512fp16` intrinsics] (rust-lang/rust#127213) (excluding those that depend directly on the unstable `f16` type) - [AArch64 NEON fp16 intrinsics] (rust-lang/rust#136306) (excluding those that depend directly on the unstable `f16` type) - [`f32::consts::EULER_GAMMA`] (https://doc.rust-lang.org/stable/std/f32/consts/constant.EULER_GAMMA.html) - [`f64::consts::EULER_GAMMA`] (https://doc.rust-lang.org/stable/std/f64/consts/constant.EULER_GAMMA.html) - [`f32::consts::GOLDEN_RATIO`] (https://doc.rust-lang.org/stable/std/f32/consts/constant.GOLDEN_RATIO.html) - [`f64::consts::GOLDEN_RATIO`] (https://doc.rust-lang.org/stable/std/f64/consts/constant.GOLDEN_RATIO.html) These previously stable APIs are now stable in const contexts: - [`f32::mul_add`] (https://doc.rust-lang.org/stable/std/primitive.f32.html#method.mul_add) - [`f64::mul_add`] (https://doc.rust-lang.org/stable/std/primitive.f64.html#method.mul_add) Cargo ----- - Stabilize the config include key. The top-level include config key allows loading additional config files, enabling better organization, sharing, and management of Cargo configurations across projects and environments. [docs] (https://doc.rust-lang.org/nightly/cargo/reference/config.html#including-extra-configuration-files) [#16284] (rust-lang/cargo#16284) - Stabilize the pubtime field in registry index. This records when a crate version was published and enables time-based dependency resolution in the future. Note that crates.io will gradually backfill existing packages when a new version is published. Not all crates have pubtime yet. [#16369] (rust-lang/cargo#16369) [#16372] (rust-lang/cargo#16372) - Cargo now parses [TOML v1.1](https://toml.io/en/v1.1.0) for manifests and configuration files. Note that using these features in Cargo.toml will raise your development MSRV, but the published manifest remains compatible with older parsers. [#16415] (rust-lang/cargo#16415) - [Make `CARGO_BIN_EXE_<crate>` available at runtime ] (rust-lang/cargo#16421) Compatibility Notes ------------------- - [Forbid freely casting lifetime bounds of `dyn`-types] (rust-lang/rust#136776) - [Make closure capturing have consistent and correct behaviour around patterns] (rust-lang/rust#138961) Some finer details of how precise closure captures get affected by pattern matching have been changed. In some cases, this can cause a non-move closure that was previously capturing an entire variable by move, to now capture only part of that variable by move, and other parts by borrow. This can cause the borrow checker to complain where it previously didn't, or cause `Drop` to run at a different point in time. - [Standard library macros are now imported via prelude, not via injected ` #[macro_use]`] (rust-lang/rust#139493) This will raise an error if macros of the same name are glob imported. For example if a crate defines their own `matches` macro and then glob imports that, it's now ambiguous whether the custom or standard library `matches` is meant and an explicit import of the name is required to resolve the ambiguity. One exception is `core::panic` and `std::panic`, if their import is ambiguous a new warning ([`ambiguous_panic_imports`] (rust-lang/rust#147319)) is raised. This may raise a new warning ([`ambiguous_panic_imports`] (rust-lang/rust#147319)) on `#![no_std]` code glob importing the std crate. Both `core::panic!` and `std::panic!` are then in scope and which is used is ambiguous. - [Don't strip shebang in expression-context `include!(…)`s] (rust-lang/rust#146377) This can cause previously working includes to no longer compile if they included files which started with a shebang. - [Ambiguous glob reexports are now also visible cross-crate] (rust-lang/rust#147984) This unifies behavior between local and cross-crate errors on these exports, which may introduce new ambiguity errors. - [Don't normalize where-clauses before checking well-formedness] (rust-lang/rust#148477) - [Introduce a future compatibility warning on codegen attributes on body-free trait methods] (rust-lang/rust#148756) These attributes currently have no effect in this position. - [On Windows `std::time::SystemTime::checked_sub_duration` will return `None` for times before the Windows epoch (1/1/1601)] (rust-lang/rust#148825) - [Lifetime identifiers such as `'a` are now NFC normalized] (rust-lang/rust#149192). - [Overhaul filename handling for cross-compiler consistency] (rust-lang/rust#149709) Any paths emitted by compiler now always respect the relative-ness of the paths and `--remap-path-prefix` given originally. One side-effect of this change is that paths emitted for local crates in Cargo (path dependencies and workspace members) are no longer absolute but relative when emitted as part of a diagnostic in a downstream crate. Internal Changes ---------------- These changes do not affect any public interfaces of Rust, but they represent significant improvements to the performance or internals of rustc and related tools. - [Switch to `annotate-snippets` for error emission] (rust-lang/rust#150032) This should preserve mostly the same outputs in rustc error messages.

rustbot assigned jdonszelmann Oct 22, 2025

rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Oct 22, 2025

rust-bors bot added a commit that referenced this pull request Oct 22, 2025

Auto merge of #147984 - petrochenkov:expambig, r=<try>

b4c5508

resolve: Preserve ambiguous glob reexports in crate metadata

This comment has been minimized.

Sign in to view

petrochenkov added S-waiting-on-crater Status: Waiting on a crater run to be completed. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Oct 22, 2025

craterbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-crater Status: Waiting on a crater run to be completed. labels Oct 24, 2025

petrochenkov 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 Oct 24, 2025

petrochenkov force-pushed the expambig branch from aa2fb6e to e388d62 Compare October 24, 2025 12:56

This comment has been minimized.

Sign in to view

rust-bors bot added a commit that referenced this pull request Oct 24, 2025

Auto merge of #147984 - petrochenkov:expambig, r=<try>

c6359cd

resolve: Preserve ambiguous glob reexports in crate metadata

petrochenkov added S-waiting-on-crater Status: Waiting on a crater run to be completed. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Oct 24, 2025

bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Dec 9, 2025

petrochenkov mentioned this pull request Dec 9, 2025

Support importing path-segment keyword with renaming #146972

Merged

bors mentioned this pull request Dec 9, 2025

Make typo in field and name suggestions verbose #149816

Merged

bors added the merged-by-bors This PR was explicitly merged by bors. label Dec 9, 2025

bors merged commit c61a3a4 into rust-lang:main Dec 9, 2025
12 checks passed

rustbot added this to the 1.94.0 milestone Dec 9, 2025

rustbot added the perf-regression Performance regression. label Dec 9, 2025

bors mentioned this pull request Dec 9, 2025

resolve: Report more visibility-related early resolution ambiguities for imports #149596

Merged

weiznich mentioned this pull request Dec 10, 2025

Diesel stops building with nightly-2025-12-10 #149845

Closed

LorrensP-2158466 mentioned this pull request Dec 17, 2025

FCW Lint when using an ambiguously glob imported trait #149058

Merged

petrochenkov mentioned this pull request Dec 29, 2025

resolve: Mark items under exported ambiguous imports as exported #150491

Merged

traviscross mentioned this pull request Jan 14, 2026

Make ambiguous_glob_reexports an FCW at deny #151146

Draft

petrochenkov mentioned this pull request Jan 15, 2026

resolve: Downgrade ambiguous_glob_imports to warn-by-default #151130

Merged

Mark-Simulacrum mentioned this pull request Jan 25, 2026

Draft release notes for 1.94.0 #151650

Closed

eggyal mentioned this pull request Feb 8, 2026

matches is ambiguous #152346

Open

Uh oh!

Conversation

petrochenkov commented Oct 22, 2025 • edited by yaahc Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

rustbot commented Oct 22, 2025

Uh oh!

petrochenkov commented Oct 22, 2025

Uh oh!

This comment has been minimized.

petrochenkov commented Oct 22, 2025

Uh oh!

rust-bors bot commented Oct 22, 2025

Uh oh!

petrochenkov commented Oct 22, 2025

Uh oh!

craterbot commented Oct 22, 2025

Uh oh!

craterbot commented Oct 22, 2025

Uh oh!

craterbot commented Oct 24, 2025

Footnotes

Uh oh!

petrochenkov commented Oct 24, 2025

Uh oh!

This comment has been minimized.

petrochenkov commented Oct 24, 2025

Uh oh!

This comment has been minimized.

rust-bors bot commented Oct 24, 2025

Uh oh!

petrochenkov commented Oct 24, 2025

Uh oh!

craterbot commented Oct 24, 2025

Uh oh!

bors commented Dec 9, 2025

Uh oh!

bors commented Dec 9, 2025

Uh oh!

Uh oh!

github-actions bot commented Dec 9, 2025

Test differences

Stage 1

Stage 2

Job duration changes

Uh oh!

rust-timer commented Dec 9, 2025

Overall result: ❌ regressions - please read the text below

Instruction count

Max RSS (memory usage)

Cycles

Binary size

Uh oh!

Kobzol commented Dec 16, 2025

Uh oh!

petrochenkov commented Dec 16, 2025

Uh oh!

petrochenkov commented Dec 16, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

15 participants

petrochenkov commented Oct 22, 2025 •

edited by yaahc

Loading