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
11 Open 29 Closed
11 Open 29 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

ICE: encountered type variable A-closures Area: Closures (`|…| { … }`) C-bug Category: This is a bug. F-unboxed_closures `#![feature(unboxed_closures)]` I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ S-bug-has-test Status: This bug is tracked inside the repo by a `known-bug` test. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#131758 opened Oct 15, 2024 by matthiaskrgr
1
Rules around call resolution on fn_traits are confusing C-discussion Category: Discussion or questions that doesn't represent real issues. F-unboxed_closures `#![feature(unboxed_closures)]` 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.
#120022 opened Jan 16, 2024 by Kolsky
2
ICE: unboxed closure but only with mir-opt-level=0 C-bug Category: This is a bug. E-needs-test Call for participation: An issue has been fixed and does not reproduce, but no test has been added. F-unboxed_closures `#![feature(unboxed_closures)]` I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ 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.
#114665 opened Aug 9, 2023 by matthiaskrgr
3
Custom Fn* trait implementation doesn't properly fallback from Fn to FnMut, or FnMut to FnOnce C-bug Category: This is a bug. F-unboxed_closures `#![feature(unboxed_closures)]` 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.
#89032 opened Sep 17, 2021 by wwylele
Specialized FnOnce impl compiles failed with a lengthy error message A-diagnostics Area: Messages for errors, warnings, and lints A-specialization Area: Trait impl specialization C-enhancement Category: An issue proposing an enhancement or a PR with one. F-specialization `#![feature(specialization)]` F-unboxed_closures `#![feature(unboxed_closures)]` 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.
#58809 opened Feb 28, 2019 by mzji
2
Cannot call implementations of the Fn* traits on references A-type-system Area: Type system C-bug Category: This is a bug. F-unboxed_closures `#![feature(unboxed_closures)]` P-medium Medium priority T-compiler Relevant to the compiler 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.
#42736 opened Jun 18, 2017 by shepmaster
1
13
rust-call call ABI is not feature gated at call-sites A-stability Area: `#[stable]`, `#[unstable]` etc. C-bug Category: This is a bug. F-unboxed_closures `#![feature(unboxed_closures)]` P-medium Medium priority T-lang Relevant to the language team, which will review and decide on the PR/issue.
#34901 opened Jul 18, 2016 by pnkfelix
@pnkfelix
7
Struct and variant constructors are not generic over lifetimes like regular functions. A-lifetimes Area: Lifetimes / regions C-enhancement Category: An issue proposing an enhancement or a PR with one. F-unboxed_closures `#![feature(unboxed_closures)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#30904 opened Jan 14, 2016 by eddyb
1
5
Tracking issue for Fn traits (unboxed_closures & fn_traits feature) B-RFC-implemented Blocker: Approved by a merged RFC and implemented but not stabilized. 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-unboxed_closures `#![feature(unboxed_closures)]` S-tracking-design-concerns Status: There are blocking design concerns. T-lang Relevant to the language team, which will review and decide on the PR/issue. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#29625 opened Nov 5, 2015 by aturon
1 of 2 tasks
67
type parameter not constrained when using closure bounds A-diagnostics Area: Messages for errors, warnings, and lints C-enhancement Category: An issue proposing an enhancement or a PR with one. D-confusing Diagnostics: Confusing error or lint that should be reworked. D-newcomer-roadblock Diagnostics: Confusing error or lint; hard to understand for new users. F-unboxed_closures `#![feature(unboxed_closures)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#25041 opened May 2, 2015 by BurntSushi
21
Unexpected trait behavior with default_type_params A-closures Area: Closures (`|…| { … }`) A-diagnostics Area: Messages for errors, warnings, and lints C-bug Category: This is a bug. F-unboxed_closures `#![feature(unboxed_closures)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#18754 opened Nov 7, 2014 by carllerche
3
ProTip! Follow long discussions with comments:>50.