T-compiler Backlog Bonanza

Meeting proposal: https://github.com/rust-lang/compiler-team/issues/484

Potential seed query: https://github.com/rust-lang/rust/issues?page=2&q=is%3Aopen+is%3Aissue+label%3AC-tracking-issue±label%3AT-libs-api±label%3AT-libs±label%3AT-lang±label%3AT-rustdoc

Labels:

  • S-tracking-ready-to-stabilize: Needs a stabilization PR (good to go
    Image Not Showing Possible Reasons
    • The image file may be corrupted
    • The server hosting the image is unavailable
    • The image path is incorrect
    • The image format is not supported
    Learn More →
    )
  • S-tracking-needs-to-bake: Needs time to bake (set a date? other criteria?)
  • S-tracking-impl-incomplete: Not code complete or blocking bugs
  • S-tracking-unimplemented: Implementation not begun
  • S-tracking-design-concerns: Blocking design concerns
    • This might be "doesn't quite seem to deliver value we hoped for" or "something doesn't feel right"
  • S-tracking-perma-unstable
    • Internal implementation detail of rustc, stdlib
  • S-tracking-needs-summary

Note: Old processed items are at the bottom

Issues processed in meeting

Processed on 2022-10-21

"Tracking Issue for #![feature(const_impl_trait)]" rust#77463

Link: https://github.com/rust-lang/rust/issues/77463

  • this is done! closed.

"Tracking Issue for -Z codegen-backend" rust#77933

Link: https://github.com/rust-lang/rust/issues/77933

Tracking Issues (input queue)

"Tracking Issue for RFC 2959: Promote aarch64-unknown-linux-gnu to a Tier-1 Rust target" rust#78251

Link: https://github.com/rust-lang/rust/issues/78251

"Tracking Issue for #![feature(pub_macro_rules)]" rust#78855

Link: https://github.com/rust-lang/rust/issues/78855

"Tracking Issue for LLVM InstrProf code coverage (current flag: -Zinstrument-coverage)" rust#79121

Link: https://github.com/rust-lang/rust/issues/79121

"Tracking issue for deprecation lint legacy_derive_helpers" rust#79202

Link: https://github.com/rust-lang/rust/issues/79202

"Tracking Issue for user-provided classnames in fenced code blocks" rust#79483

Link: https://github.com/rust-lang/rust/issues/79483

"Tracking Issue for Non-Lexical Constant Propagation" rust#80038

Link: https://github.com/rust-lang/rust/issues/80038

"Tracking Issue for const_refs_to_cell" rust#80384

Link: https://github.com/rust-lang/rust/issues/80384

"Tracking issue for only producing .xz on CI" rust#80753

Link: https://github.com/rust-lang/rust/issues/80753

"Tracking Issue for {BTreeMap,BTreeSet}::drain" rust#81074

Link: https://github.com/rust-lang/rust/issues/81074

"[rustdoc-json] Output is currently under-tested" rust#81359

Link: https://github.com/rust-lang/rust/issues/81359

"Tracking Issue for the C-cmse-nonsecure-call ABI" rust#81391

Link: https://github.com/rust-lang/rust/issues/81391

"Tracking Issue for linking modifiers for native libraries " rust#81490

Link: https://github.com/rust-lang/rust/issues/81490

"Tracking Issue for mir-inlining" rust#81567

Link: https://github.com/rust-lang/rust/issues/81567

"Tracking issue for forbidden_lint_groups " rust#81670

Link: https://github.com/rust-lang/rust/issues/81670

"Follow-up work for download-rustc" rust#81930

Link: https://github.com/rust-lang/rust/issues/81930

"Tracking Issue for -Z macro-backtrace" rust#82068

Link: https://github.com/rust-lang/rust/issues/82068

"Tracking Issue for #[repr(align(...))] on function items (fn_align)" rust#82232

Link: https://github.com/rust-lang/rust/issues/82232

"Tracking Issue for RFC 3013: Checking conditional compilation at compile time" rust#82450

Link: https://github.com/rust-lang/rust/issues/82450

"Tracking Issue for future-incompatibility warning unaligned_references" rust#82523

Link: https://github.com/rust-lang/rust/issues/82523

"Tracking Issue for -Z normalize-docs" rust#82692

Link: https://github.com/rust-lang/rust/issues/82692

"Tracking Issue for proc_macro_back_compat" rust#83125

Link: https://github.com/rust-lang/rust/issues/83125

"Tracking Issue for must_not_suspend lint (RFC #3014)" rust#83310

Link: https://github.com/rust-lang/rust/issues/83310

"Tracking Issue for large_assignments lint" rust#83518

Link: https://github.com/rust-lang/rust/issues/83518

"Tracking Issue for -C export-executable-symbols" rust#84161

Link: https://github.com/rust-lang/rust/issues/84161

"Tracking issue for function attribute #[no_coverage]" rust#84605

Link: https://github.com/rust-lang/rust/issues/84605

"Tracking Issue for -Z terminal-width" rust#84673

Link: https://github.com/rust-lang/rust/issues/84673

"Tracking Issue for rustdoc --test-run-directory" rust#84674

Link: https://github.com/rust-lang/rust/issues/84674

"Tracking Issue for GenericArg::Infer" rust#85077

Link: https://github.com/rust-lang/rust/issues/85077

"Tracking Issue for async {} blocks in const expressions" rust#85368

Link: https://github.com/rust-lang/rust/issues/85368

"Tracking Issue for llvm-tools-preview" rust#85658

Link: https://github.com/rust-lang/rust/issues/85658

"Tracking Issue for RFC 3107: derive_default_enum" rust#87517

Link: https://github.com/rust-lang/rust/issues/87517

"Tracking Issue for for-loops in constants" rust#87575

Link: https://github.com/rust-lang/rust/issues/87575

"Tracking issue for UNSUPPORTED_CALLING_CONVENTIONS future compatibility lint" rust#87678

Link: https://github.com/rust-lang/rust/issues/87678

"Tracking issue for RFC 3119: Rust-lang crate ownership policy" rust#88867

Link: https://github.com/rust-lang/rust/issues/88867

"Tracking Issue for -Z remap-cwd-prefix" rust#89434

Link: https://github.com/rust-lang/rust/issues/89434

"Tracking Issue for LLVM Control Flow Integrity (CFI) Support for Rust" rust#89653

Link: https://github.com/rust-lang/rust/issues/89653

"Tracking Issue for -Z no-unique-section-names" rust#90275

Link: https://github.com/rust-lang/rust/issues/90275

"Tracking Issue for Associated Const Equality" rust#92827

Link: https://github.com/rust-lang/rust/issues/92827

"Tracking Issue for const offset_from (const_ptr_offset_from)" rust#92980

Link: https://github.com/rust-lang/rust/issues/92980

"Tracking Issue for asm_const" rust#93332

Link: https://github.com/rust-lang/rust/issues/93332

"Tracking Issue for asm_sym" rust#93333

Link: https://github.com/rust-lang/rust/issues/93333

"Tracking Issue for asm_unwind" rust#93334

Link: https://github.com/rust-lang/rust/issues/93334

"Tracking Issue for asm_experimental_arch" rust#93335

Link: https://github.com/rust-lang/rust/issues/93335

"Tracking Issue for const_fn_trait_bound" rust#93706

Link: https://github.com/rust-lang/rust/issues/93706

"Tracking Issue for control-flow enforcement technology (CET)" rust#93754

Link: https://github.com/rust-lang/rust/issues/93754

"Tracking Issue for used_with_arg" rust#93798

Link: https://github.com/rust-lang/rust/issues/93798

"Tracking Issue for post #89862 cleanup" rust#94483

Link: https://github.com/rust-lang/rust/issues/94483

Processed issues (2022-03-04 meeting)

Meeting record (zulip archive)

"Implement where clauses" rust#17657

Link: https://github.com/rust-lang/rust/issues/17657

Tagged S-tracking-impl-incomplete, S-tracking-unimplemented, T-lang

"Parse and accept type equality constraints in where clauses" rust#20041

Link: https://github.com/rust-lang/rust/issues/20041

Tagged S-tracking-design-concerns,

"Tracking issue for Consistent no-prelude attribute (RFC 501)" rust#20561

Link: https://github.com/rust-lang/rust/issues/20561

tag with S-tracking-design-concerns, and fcp close

"Tracking issue for FastISel" rust#26600

Link: https://github.com/rust-lang/rust/issues/26600

Not a tracking issue, untagging. Also close?

"Projections, lifetimes, and WF tracking issue (RFC 1214)" rust#27579

Link: https://github.com/rust-lang/rust/issues/27579

label +T-lang +WG-traits +S-tracking-needs-summary

"Tracking issue for Allow a re-export for main (RFC 1260)" rust#28937

Link: https://github.com/rust-lang/rust/issues/28937

+T-lang +I-lang-nominated

"Create a benchmark suite for uncovering runtime regressions" rust#31265

Link: https://github.com/rust-lang/rust/issues/31265

Close/move to rustc-perf repo

"Tracking issue for #[link(kind)] connecting libraries on Windows" rust#37403

Link: https://github.com/rust-lang/rust/issues/37403

+S-tracking-needs-summary

"debuginfo: How to (ideally) represent reference and pointer types in DWARF" rust#37504

Link: https://github.com/rust-lang/rust/issues/37504

Not a tracking issue

"Tracking issue to stabilize –print target-spec-json" rust#38338

Link: https://github.com/rust-lang/rust/issues/38338

-T-dev-tools +T-compiler +S-tracking-design-concerns

Processed issues (2022-03-18 meeting)

"NVPTX backend metabug" rust#38789

Link: https://github.com/rust-lang/rust/issues/38789

  • pnkfelix left comment. Marked S-tracking-needs-summary

"Tracking issue for MIR-only RLIBs" rust#38913

Link: https://github.com/rust-lang/rust/issues/38913

  • Does this really classify as a tracking issue? Should probably track implementation, but needs a direction, I think. - Jack
  • pnkfelix is leaving this on our queue to get visibility; eddyb had very interesting thoughts on doing this just for libcore through libstd to improve rustc development cycle time.
  • Discussed in meeting. We decided that this is at best S-tracking-unimplemented, but it also just represents an experimental idea that was being floated around, not something that anyone committed to.
  • pnkfelix left comment saying that this needs an MCP, not a tracking issue, and closed.

"Tracking issue for resolve_trait_on_defaulted_unit compatibility lint" rust#39216

Link: https://github.com/rust-lang/rust/issues/39216

  • This has a blocking bug #51125
  • pnkfelix left comment and tagged as S-tracking-impl-incomplete due to the blocking bug.

"Tracking issue for sanitizer support" rust#39699

Link: https://github.com/rust-lang/rust/issues/39699

  • pnkfelix left comment and tagged as S-tracking-needs-summary.
  • wesley also noted that there may be design concerns; they said they would follow up async on issue with that, and tag as necessary.

"Tracking issue for 1.0.0 tracking issues" rust#39954

Link: https://github.com/rust-lang/rust/issues/39954

  • Are these "meta" tracking issues helpful? I ticked off the checkboxes where the linked issue is closed. - Jack
  • meeting attendees agreed that a meta-tracking issue like this isn't as useful anymore, especially given that we are now doing things like the backlog bonanzas to work through the old issue queue.
  • pnkfelix left comment and closed.

"Metaissue for Visual Studio debugging Rust" rust#40460

Link: https://github.com/rust-lang/rust/issues/40460

  • Maybe reclassify as T-devtools? Or just close this in favor of specific issues. - Jack
  • meeting attendees agreed that an ever growing wish list of desired features is not a good tracking issue. (It will never get closed.)
  • better to have an established set of goals in an issue, and open up new issues with new goals.
  • pnkfelix left comment and closed

"Tracking issue for the thiscall calling convention" rust#42202

Link: https://github.com/rust-lang/rust/issues/42202

  • There is a comment for stabilization, but also a question of duplication of a everything but the abi for a function.
  • Wesley noted that this needs more tests; there were signs as of 6 months ago that the feature was broken on LLVM's side, w.r.t. name mangling, and nothing on the rustc test suite had to be updated accordingly, which to Wesley indicates that the test coverage is insufficient.
  • pnkfelix had several concerns, mostly reflecting the points raised in comment thread of issue
    • but, allowing macro expansion in for the ABI in extern ABI might be a reasonable way to work-around the concerns raised there.
  • pnkfelix left a comment and tagged as S-tracking-design-concerns (w.r.t. the code duplication issue that was raised) and S-tracking-needs-summary (w.r.t. current lint behavior vs other similar ABI variations).

"underscore_literal_suffix future-compatibility warnings" rust#42326

Link: https://github.com/rust-lang/rust/issues/42326

  • Underscores after float literals have been an error since May 2017; underscore after string literal has been warn since then. Can probably change underscore after string literal to deny-by-default.
  • team discussed options here: either do a crater run (with upgrade to hard error), or rewrite as proper lint
  • pnkfelix left comment outlining options and tagged as S-tracking-needs-to-bake

Processed items

Pre-processed issues (prior to 2022-03-17 meeting)

"Tracking issue for the "ptx-kernel" ABI" rust#38788

Link: https://github.com/rust-lang/rust/issues/38788

  • pnkfelix left comment. Marked S-tracking-design-concerns and S-tracking-needs-summary

Pre-processed issues (prior to XX)

"In-band lifetimes: Lint against single-use lifetime names" rust#44752

Link: https://github.com/rust-lang/rust/issues/44752

  • jackh726 left comment. Marked S-tracking-impl-incomplete.

"tracking issue for the Traits Working Group" rust#48416

Link: https://github.com/rust-lang/rust/issues/48416

  • jackh726 left comment and closed.

"tracking issue for lifetime inference error work (E0495)" rust#42516

Link: https://github.com/rust-lang/rust/issues/42516

  • There are still linked issues that are open. It's not clear that having this issue open is helpful. -Jack
  • left comment and closed -pnkfelix

"Tracking issue for -Z profile " rust#42524

Link: https://github.com/rust-lang/rust/issues/42524

  • Changed to T-compiler from T-dev-tools and added S-tracking-needs-summary

"Reconsider using SVH for loading transitive crate dependencies" rust#42677

Link: https://github.com/rust-lang/rust/issues/42677

  • commented, removed C-tracking-issue and added various A-labels to clarify what it is relevant to.

"Altivec/VSX support" rust#42743

Link: https://github.com/rust-lang/rust/issues/42743

  • Left comment; seems correctly categorized, just stalled for now due to lack of developer investment.

"change how MIR inlining handles cycles" rust#43542

Link: https://github.com/rust-lang/rust/issues/43542

  • Revised metadata, commented, and closed.

"Stabilise -Zsave-analysis" rust#43606

Link: https://github.com/rust-lang/rust/issues/43606

  • AFAIK, this is still used for rls. But we'd prefer to remove this eventually? -Jack
  • Leaving comment that we want to remove eventually, changing labels and title

"MIR optimization tracking issue." rust#44285

Link: https://github.com/rust-lang/rust/issues/44285

  • Mention in wg-mir-opt zulip stream and clsoed as not a tracking issue

processed on 2022-05-06

"Tracking issue: RFC 2103 - attributes for tools" rust#44690

Link: https://github.com/rust-lang/rust/issues/44690

  • Changing to T-compiler from T-dev-tools
  • commented that it could use an update as to its current status
  • added S-tracking-impl-incomplete

"Tracking issue: Allow autoderef and autoref in operators (experiment)" rust#44762

Link: https://github.com/rust-lang/rust/issues/44762

  • appears to have some prototype work from a contributor
  • marked as S-tracking-unimplemented, and asked contributor if they need help putting up a PR for their efforts

"Move more of src/rustllvm to upstream LLVM" rust#46437

Link: https://github.com/rust-lang/rust/issues/46437

  • marked as S-tracking-impl-incomplete

processed on 2022-05-27

"Tracking Issue for Incremental Compilation" rust#47660

Link: https://github.com/rust-lang/rust/issues/47660

  • marked as S-tracking-impl-incomplete

"codegen-units + ThinLTO is not as good as codegen-units = 1" rust#47745

Link: https://github.com/rust-lang/rust/issues/47745

  • removed C-tracking-issue

"tracking issue for "chalkification"" rust#48049

Link: https://github.com/rust-lang/rust/issues/48049

  • marked as S-tracking-impl-incomplete and S-tracking-needs-summary

"Compiler Performance Tracking Issue" rust#48547

Link: https://github.com/rust-lang/rust/issues/48547

  • we should port this excellent content to the rustc-dev-guide (and then close this issue with a link to that page/chapter)
  • marked as S-tracking-impl-incomplete

"Compiler Performance: Benchmark Definitions" rust#48750

Link: https://github.com/rust-lang/rust/issues/48750

  • closed

"Tracking issue for libtest JSON output" rust#49359

Link: https://github.com/rust-lang/rust/issues/49359

  • Changed T-dev-tools to T-compiler
  • We're not sure this belongs in our bucket. Kicking it over to T-libs-api instead.

"Tracking issue for generalized two-phase borrows" rust#49434

Link: https://github.com/rust-lang/rust/issues/49434

  • pnkfelix left comment
  • moved to T-types and adding S-tracking-design-concerns:

processed on 2022-06-03

"Expand the Rust Bookshelf 📚" rust#49453

Link: https://github.com/rust-lang/rust/issues/49453

Bounce to T-lang (maybe they decide to bounce to T-core)

"Add compiler-internal lints" rust#49509

Link: https://github.com/rust-lang/rust/issues/49509

Tagged E-help-wanted and S-tracking-impl-incomplete

"Spurious linker error with armv7-unknown-linux-gnueabihf-gcc: relocation truncated to fit: R_ARM_THM_JUMP24 against symbol" rust#49845

Link: https://github.com/rust-lang/rust/issues/49845

Closing - old issue with no recent problems

"Diagnostics Revamp Roadmap" rust#51528

Link: https://github.com/rust-lang/rust/issues/51528

Adding S-tracking-impl-incomplete and S-tracking-needs-summary

processed on 2022-06024

"Abort instead of unwinding past FFI functions" rust#52652

Link: https://github.com/rust-lang/rust/issues/52652

Tagged WG-project-ffi-unwind and S-tracking-needs-summary

"Tracking issue for -Z emit-stack-sizes" rust#54192

Link: https://github.com/rust-lang/rust/issues/54192

Tagged S-tracking-needs-summary

"Tracking issue for RFC 2437, "Rustfmt stability"" rust#54504

Link: https://github.com/rust-lang/rust/issues/54504

Skipped: not our team

"Tracking issue for warning for rust_2018_idioms by default" rust#54910

Link: https://github.com/rust-lang/rust/issues/54910

Tagged S-tracking-impl-incomplete

"Tracking issue for trait alias implementation (RFC 1733)" rust#55628

Link: https://github.com/rust-lang/rust/issues/55628

Tagged WG-traits and S-tracking-needs-summary

"run-pass tests: Some tests are really slow (… has been running for over 60 seconds)" rust#55841

Link: https://github.com/rust-lang/rust/issues/55841

Closed due to inactivity

"tracking issue for "universe transition"" rust#56105

Link: https://github.com/rust-lang/rust/issues/56105

Tagged WG-traits and S-tracking-impl-incomplete

"Tracking issue: –persist-doctests flag for rustdoc" rust#56925

Link: https://github.com/rust-lang/rust/issues/56925

Skipped: not our team

"NLL: complete transition from migrate to full NLL" rust#57895

Link: https://github.com/rust-lang/rust/issues/57895

Issue was already closed

"Tracking Issue for making incremental compilation the default for Release Builds" rust#57968

Link: https://github.com/rust-lang/rust/issues/57968

Tagged S-tracking-design-concerns

"NLL: turn off migration mode" rust#58781

Link: https://github.com/rust-lang/rust/issues/58781

Issue was already closed

"Tracking issue for musl host toolchain" rust#59302

Link: https://github.com/rust-lang/rust/issues/59302

Tagged S-tracking-impl-incomplete

"Spurious failure "failed to remove file … Access is denied" in cargo test profile_selection_check_all_targets* on Windows" rust#56040

Link: https://github.com/rust-lang/rust/issues/56040

Closed due to inactivity

"Spurious SIGILL (signal 4) when linking with cc on macOS during doctest" rust#58209

Link: https://github.com/rust-lang/rust/issues/58209

Closed due to inactivity

Processed on 2022-08-12

"eventual goal: re-remove leak-check from compiler " rust#59490

Link: https://github.com/rust-lang/rust/issues/59490

  • there was an update here 28 days ago from T-types:

discussed in the t-types backlog bonanza

While the plan for how we want to remove the leak check has changed, we still intend to remove the current version, so we're keeping this open to track that for now.

The goal is to pretty much add a param_env aware leak check directly into trait solving and remove the current impl.

  • added S-tracking-unimplemented

"Tracking issue for RFC 2603, "Rust Symbol Mangling (v0)"" rust#60705

Link: https://github.com/rust-lang/rust/issues/60705

Left comment: https://github.com/rust-lang/rust/issues/60705#issuecomment-1213168334

  • Added S-tracking-needs-to-bake

"Add missing long error code explanations" rust#61137

Link: https://github.com/rust-lang/rust/issues/61137

  • Removed C-tracking-issue and added metabug label.

"Tracking issue for -Z binary-dep-depinfo" rust#63012

Link: https://github.com/rust-lang/rust/issues/63012

"Decide whether to suggest anything when encountering break and expecting !" rust#63390

Link: https://github.com/rust-lang/rust/issues/63390

"Tracking issue for dual-proc-macros" rust#64671

Link: https://github.com/rust-lang/rust/issues/64671

Processed on 2022-09-09

"create a lint for tracking "tainted" fallback around abrupt expressions and ! type" rust#66173

  • left comment, tagged as S-tracking-design-concerns, and closed

Link: https://github.com/rust-lang/rust/issues/66173

"Tracking issue for check_invalid_html_tags" rust#67799

Link: https://github.com/rust-lang/rust/issues/67799

  • left comment but otherwise skipped as a T-rustdoc specific item

"Tracking Issue for Generator Memory Usage" rust#69826

Link: https://github.com/rust-lang/rust/issues/69826

  • not really a tracking issue in the sense of C-tracking-issue
  • left comment, added metabug and removed C-tracking-issue

"Tracking Issue for -Z src-hash-algorithm" rust#70401

Link: https://github.com/rust-lang/rust/issues/70401

  • open question about whether this should be command line flag, or part of the target specification.
  • left comment, tagged as S-tracking-needs-summary

"Cargotest enhancements" rust#70659

Link: https://github.com/rust-lang/rust/issues/70659

  • T-infra, skipped

"Tracking issue for generator code quality" rust#71407

Link: https://github.com/rust-lang/rust/issues/71407

  • not really a tracking issue in the sense of C-tracking-issue
  • left comment, added metabug and removed C-tracking-issue

"Tracking Issue for making ptr offset methods "const fn"" rust#71499

Link: https://github.com/rust-lang/rust/issues/71499

  • already closed as complete

"Use lld by default on x64 Ubuntu 20.04 LTS" rust#71515

Link: https://github.com/rust-lang/rust/issues/71515

  • lqd's work on compiler-team#510 is meant to address this
  • left comment and tagged as S-tracking-impl-incomplete

"Use lld by default on x64 msvc windows" rust#71520

Link: https://github.com/rust-lang/rust/issues/71520

  • left comment, tagged as S-tracking-needs-summary

"Tracking issue for Lazy Normalization of Constants" rust#72219

Link: https://github.com/rust-lang/rust/issues/72219

  • already closed by lcnr as "having no purpose"
  • skipping in meeting

"Tracking issue for supporting macOS on Apple Silicon (a.k.a arm64, M1, aarch64)" rust#73908

Link: https://github.com/rust-lang/rust/issues/73908

  • left comment, marked S-tracking-impl-incomplete

Processed on 2022-09-16

"Tracking Issue for tracked access to environment variables from proc macros" rust#74690

Link: https://github.com/rust-lang/rust/issues/74690

  • This was closed back on 2022-07-20 in favor of #99515

"Tracking issue for new LLVM pass manager (-Znew-llvm-pass-manager)" rust#74705

Link: https://github.com/rust-lang/rust/issues/74705

"Tracking Issue for assert_eq in constants" rust#74925

Link: https://github.com/rust-lang/rust/issues/74925

  • should either close or removing C-tracking-issue label

"Tracking Issue for the use of ? in constants" rust#74935

  • should either close or removing C-tracking-issue label

Link: https://github.com/rust-lang/rust/issues/74935

"Tracking issue for const <*const T>::is_null" rust#74939

Link: https://github.com/rust-lang/rust/issues/74939

Processed on 2022-09-23

"Tracking Issue for const MaybeUninit::as(_mut)_ptr (feature: const_maybe_uninit_as_ptr)" rust#75251

Link: https://github.com/rust-lang/rust/issues/75251

  • left comment, added label: +T-libs +S-tracking-needs-summary

"Tracking Issue for improved item code blocks" rust#75303

Link: https://github.com/rust-lang/rust/issues/75303

  • S-tracking-unimplemented

"Tracking Issue for pointer methods returning MaybeUninit<T>" rust#75402

Link: https://github.com/rust-lang/rust/issues/75402

  • S-tracking-design-concerns

Processed on 2022-10-14

"Tracking Issue for defaulting to DWARF 5 format" rust#75890

Link: https://github.com/rust-lang/rust/issues/75890

"Tracking issue for const Ordering methods" rust#76113

Link: https://github.com/rust-lang/rust/issues/76113

  • left comment, added T-libs-api and S-tracking-need-summary

"Tracking Issue for const_caller_location" rust#76156

Link: https://github.com/rust-lang/rust/issues/76156

  • Not clear whether this is useful to stabilize without also stably providing Location accessors in stable.
  • left comment, tagged with S-tracking-needs-to-bake

"Tracking issue for MIR-level integer range analysis" rust#76579

Link: https://github.com/rust-lang/rust/issues/76579

  • not a real tracking issue in sense intended by C-tracking-issue. added comment and removed label.

"Support stack probing for arm64 (aarch64)" rust#77071

Link: https://github.com/rust-lang/rust/issues/77071

  • left comment, tagged as unimplemented
Select a repo