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
15 Open 4 Closed
15 Open 4 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

Box sometimes forgets to drop its allocator when the Box is conditionally initialized. A-allocators Area: Custom and system allocators A-box Area: Our favorite opsem complication A-MIR Area: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.html C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#131082 opened Oct 1, 2024 by theemathas
1
@beepster4096
2
Tracking Issue for box_vec_non_null A-box Area: Our favorite opsem complication C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#130364 opened Sep 14, 2024 by theemathas
1 of 3 tasks
1
Tracking Issue for box_as_ptr A-box Area: Our favorite opsem complication C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-libs Relevant to the library team, which will review and decide on the PR/issue.
#129090 opened Aug 14, 2024 by RalfJung
1 of 4 tasks
2
Vec::into_boxed_slice no-excess guarantee regressed in 1.77.0 A-box Area: Our favorite opsem complication A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools C-bug Category: This is a bug. E-help-wanted Call for participation: Help is requested to fix this issue. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#125941 opened Jun 3, 2024 by str4d
3
Box::leak will not call allocator destruction function A-allocators Area: Custom and system allocators A-box Area: Our favorite opsem complication C-bug Category: This is a bug. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#106207 opened Dec 28, 2022 by yuhao-su
8
Box documentation regarding allocation for ZSTs A-box Area: Our favorite opsem complication A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools C-bug Category: This is a bug. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#104039 opened Nov 6, 2022 by zdivelbiss
Boxes with custom allocators break several underlying assumptions in Miri (and MIR more broadly) A-allocators Area: Custom and system allocators A-box Area: Our favorite opsem complication A-MIR Area: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.html C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#95453 opened Mar 30, 2022 by autumnontape
27
noalias on a Box doesn't seem to have an impact when compiling without -C panic=abort A-box Area: Our favorite opsem complication A-codegen Area: Code generation C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#95323 opened Mar 26, 2022 by jrmuizel
6
Could the compiler automatically re-use Box allocations as an optimization? A-box Area: Our favorite opsem complication A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-mir-opt Area: MIR optimizations C-discussion Category: Discussion or questions that doesn't represent real issues. I-slow Issue: Problems and improvements with respect to performance of generated code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#93707 opened Feb 6, 2022 by scottmcm
4
slow compilation of large struct with Box-members and ? in field init A-box Area: Our favorite opsem complication A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. I-compiletime Issue: Problems and improvements with respect to compile times. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#93257 opened Jan 24, 2022 by M1cha
2
Tracking Issue for const_box A-box Area: Our favorite opsem complication C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC F-const_trait_impl `#![feature(const_trait_impl)]` T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#92521 opened Jan 3, 2022 by lilasta
1 of 3 tasks
8
&Box<[T]> does not impl IntoIterator A-box Area: Our favorite opsem complication A-iterators Area: Iterators C-feature-request Category: A feature request, i.e: not implemented / a PR. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#83589 opened Mar 27, 2021 by lopopolo
4
Boxing zeroed arrays and slices uses rust_alloc + memset instead of rust_alloc_zeroed A-box Area: Our favorite opsem complication C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#80752 opened Jan 6, 2021 by leonardo-m
1
Tracking Issue for box_into_inner A-box Area: Our favorite opsem complication C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. Libs-Tracked Libs issues that are tracked on the team's project board. proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#80437 opened Dec 28, 2020 by crlf0710
1 of 4 tasks
81
Stack overflow with Boxed array A-box Area: Our favorite opsem complication A-codegen Area: Code generation A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#53827 opened Aug 30, 2018 by opus111
45
ProTip! no:milestone will show everything without a milestone.