Search results

Trivial bounds check doesn't consider non-global predicates *after* normalization

C-bugCategory: This is a bug.Category: This is a bug.

T-typesRelevant to the types team, which will review and decide on the PR/issue.Relevant to the types team, which will review and decide on the PR/issue.

Status: Open.

#140309 In rust-lang/rust;

· compiler-errors opened on Apr 25, 2025

Incomplete inference guidance due to <code>Sized</code> param-env clause causes method selection failure

A-inferenceArea: Type inferenceArea: Type inference

A-trait-systemArea: Trait systemArea: Trait system

C-bugCategory: This is a bug.Category: This is a bug.

fixed-by-next-solverFixed by the next-generation trait solver, `-Znext-solver`.Fixed by the next-generation trait solver, `-Znext-solver`.

T-typesRelevant to the types team, which will review and decide on the PR/issue.Relevant to the types team, which will review and decide on the PR/issue.

Status: Open.

#137812 In rust-lang/rust;

· compiler-errors opened on Feb 28, 2025

Reword <code>?Trait</code> bound diagnostic

A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lints

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#136944 In rust-lang/rust;

· compiler-errors opened on Feb 12, 2025

Lifetime generics on Generic Const Items should not affect if const is checked for evaluatability

C-bugCategory: This is a bug.Category: This is a bug.

F-generic_const_items`#![feature(generic_const_items)]``#![feature(generic_const_items)]`

T-typesRelevant to the types team, which will review and decide on the PR/issue.Relevant to the types team, which will review and decide on the PR/issue.

Status: Open.

#136204 In rust-lang/rust;

· compiler-errors opened on Jan 28, 2025

Robustify the <code>TyKind</code> ambig/unambig layout compatibility tests

C-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#135944 In rust-lang/rust;

· compiler-errors opened on Jan 23, 2025

Better error reporting for <code>T: ?Sized</code> types when <code>impl Receiver for MyType&lt;T&gt;</code> is implicitly sized

A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lints

C-discussionCategory: Discussion or questions that doesn't represent real issues.Category: Discussion or questions that doesn't represent real issues.

D-confusingDiagnostics: Confusing error or lint that should be reworked.Diagnostics: Confusing error or lint that should be reworked.

F-arbitrary_self_types`#![feature(arbitrary_self_types)]``#![feature(arbitrary_self_types)]`

Status: Open.

#134390 In rust-lang/rust;

· compiler-errors opened on Dec 16, 2024

<code>compare_method_predicate_entailment</code> is missing implied bounds from higher-ranked GAT

A-GATsArea: Generic associated types (GATs)Area: Generic associated types (GATs)

A-higher-rankedArea: Higher-ranked things (e.g., lifetimes, types, trait bounds aka HRTBs)Area: Higher-ranked things (e.g., lifetimes, types, trait bounds aka HRTBs)

A-implied-boundsArea: Implied bounds / inferred outlives-boundsArea: Implied bounds / inferred outlives-bounds

A-trait-systemArea: Trait systemArea: Trait system

C-bugCategory: This is a bug.Category: This is a bug.

T-typesRelevant to the types team, which will review and decide on the PR/issue.Relevant to the types team, which will review and decide on the PR/issue.

Status: Open.

#133805 In rust-lang/rust;

· compiler-errors opened on Dec 3, 2024

Tracking Issue for <code>const_destruct</code>

C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFC

F-const_trait_impl`#![feature(const_trait_impl)]``#![feature(const_trait_impl)]`

PG-const-traitsProject group: Const traitsProject group: Const traits

T-langRelevant to the language team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.

T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.

T-typesRelevant to the types team, which will review and decide on the PR/issue.Relevant to the types team, which will review and decide on the PR/issue.

Status: Open.

#133214 In rust-lang/rust;

· compiler-errors opened on Nov 19, 2024

Tracking Issue for <code>async_fn_in_dyn_trait</code>

B-experimentalBlocker: In-tree experiment; RFC pending, not yet approved or unneeded (requires FCP to stabilize).Blocker: In-tree experiment; RFC pending, not yet approved or unneeded (requires FCP to stabilize).

C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFC

F-async_fn_in_dyn_trait`#![feature(async_fn_in_dyn_trait)]``#![feature(async_fn_in_dyn_trait)]`

T-langRelevant to the language team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.

Status: Open.

#133119 In rust-lang/rust;

· compiler-errors opened on Nov 16, 2024

<code>~const</code> is allowed on structs (and other bad positions) within <code>const fn</code>.

C-bugCategory: This is a bug.Category: This is a bug.

F-const_trait_impl`#![feature(const_trait_impl)]``#![feature(const_trait_impl)]`

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#132067 In rust-lang/rust;

· compiler-errors opened on Oct 23, 2024

Further restricting what coercions are allowed on places of type <code>!</code>

A-coercionsArea: implicit and explicit `expr as Type` coercionsArea: implicit and explicit `expr as Type` coercions

C-discussionCategory: Discussion or questions that doesn't represent real issues.Category: Discussion or questions that doesn't represent real issues.

F-never_type`#![feature(never_type)]``#![feature(never_type)]`

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

T-opsemRelevant to the opsem teamRelevant to the opsem team

Status: Open.

#131297 In rust-lang/rust;

· compiler-errors opened on Oct 5, 2024

Stack overflow with <code>clashing_extern_declarations</code>

A-lintsArea: Lints (warnings about flaws in source code) such as unused_mut.Area: Lints (warnings about flaws in source code) such as unused_mut.

C-bugCategory: This is a bug.Category: This is a bug.

I-crashIssue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#130947 In rust-lang/rust;

· compiler-errors opened on Sep 27, 2024