Skip to content

Issues: rust-lang/rust

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
17 Open 36 Closed
17 Open 36 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

2024 edition regression: cannot write blanket implementation for closures that return the Never type A-edition-2024 Area: The 2024 edition F-never_type `#![feature(never_type)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-edition Relevant to the edition team. T-types Relevant to the types team, which will review and decide on the PR/issue.
#139610 opened Apr 10, 2025 by alice-i-cecile
7
Result type inference breaks in 2024 edition, while working correctly in 2021 edition A-coercions Area: implicit and explicit `expr as Type` coercions A-inference Area: Type inference C-bug Category: This is a bug. F-never_type `#![feature(never_type)]` T-types Relevant to the types team, which will review and decide on the PR/issue.
#135864 opened Jan 22, 2025 by nazar-pc
9
Further restricting what coercions are allowed on places of type ! A-coercions Area: implicit and explicit `expr as Type` coercions C-discussion Category: Discussion or questions that doesn't represent real issues. F-never_type `#![feature(never_type)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#131297 opened Oct 5, 2024 by compiler-errors
6
unreachable_patterns fires on match arm that can't be removed. A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. D-invalid-suggestion Diagnostics: A structured suggestion resulting in incorrect code. F-never_type `#![feature(never_type)]` L-unreachable_patterns Lint: unreachable_patterns T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#129352 opened Aug 21, 2024 by Dirbaio
15
Bad interaction between never_type, try_blocks, and From/Into C-bug Category: This is a bug. F-never_type `#![feature(never_type)]` F-try_blocks `#![feature(try_blocks)]` S-has-mcve Status: A Minimal Complete and Verifiable Example has been found for this issue T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#125364 opened May 21, 2024 by ia0
2
! can't be cast to Fn(_) -> _ C-discussion Category: Discussion or questions that doesn't represent real issues. F-never_type `#![feature(never_type)]`
#120153 opened Jan 20, 2024 by Pr0methean
10
Non-exhaustive pattern error when matching on ! C-bug Category: This is a bug. F-never_type `#![feature(never_type)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#115716 opened Sep 9, 2023 by cjgillot
2
Return-position impl Trait is not satisfied by divergent/never type A-diagnostics Area: Messages for errors, warnings, and lints A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools A-trait-system Area: Trait system F-never_type `#![feature(never_type)]` T-lang Relevant to the language team, which will review and decide on the PR/issue. T-types Relevant to the types team, which will review and decide on the PR/issue.
#113875 opened Jul 20, 2023 by wchargin
@fmease
18
((), !) and ((), ()) are considered incompatible types C-bug Category: This is a bug. F-never_type `#![feature(never_type)]` P-low Low priority regression-from-stable-to-stable Performance or correctness regression from one stable version to another. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#112856 opened Jun 20, 2023 by GrigorenkoPV
3
Semicolon after diverging try operator shouldn't matter C-discussion Category: Discussion or questions that doesn't represent real issues. F-never_type `#![feature(never_type)]` T-types Relevant to the types team, which will review and decide on the PR/issue.
#106357 opened Jan 1, 2023 by clarfonthey
8
! cannot be used as impl Trait when ! implements Trait C-bug Category: This is a bug. F-never_type `#![feature(never_type)]` requires-nightly This issue requires a nightly compiler in some way. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#105284 opened Dec 5, 2022 by zachs18
8
uninhabited enum variants still block auto trait implementation F-never_type `#![feature(never_type)]` T-lang Relevant to the language team, which will review and decide on the PR/issue.
#101083 opened Aug 27, 2022 by soqb
1
Casting or adding type ascription to panic!() triggers unreachable_code A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. C-enhancement Category: An issue proposing an enhancement or a PR with one. F-never_type `#![feature(never_type)]` P-medium Medium priority requires-nightly This issue requires a nightly compiler in some way. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#67227 opened Dec 11, 2019 by leo60228
7
Allow unused_must_use on result with never type A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. C-enhancement Category: An issue proposing an enhancement or a PR with one. F-never_type `#![feature(never_type)]` T-lang Relevant to the language team, which will review and decide on the PR/issue.
#65861 opened Oct 27, 2019 by TheZoq2
2
We should lint when !-fallback results in questionable code A-diagnostics Area: Messages for errors, warnings, and lints A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. C-enhancement Category: An issue proposing an enhancement or a PR with one. F-never_type `#![feature(never_type)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#46162 opened Nov 21, 2017 by canndrew
1
Go over all libstd traits and see which of them !/TyNever should implement C-feature-accepted Category: A feature request that has been accepted pending implementation. F-never_type `#![feature(never_type)]` T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#35866 opened Aug 20, 2016 by arielb1
1
Tracking issue for promoting ! to a type (RFC 1216) A-type-system Area: Type system B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC F-never_type `#![feature(never_type)]` Libs-Tracked Libs issues that are tracked on the team's project board. S-tracking-needs-to-bake Status: The implementation is "complete" but it needs time to bake. T-lang Relevant to the language team, which will review and decide on the PR/issue. T-types Relevant to the types team, which will review and decide on the PR/issue.
#35121 opened Jul 29, 2016 by nikomatsakis
2 tasks
@WaffleLapkin
376
ProTip! Follow long discussions with comments:>50.