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
7 Open 8 Closed
7 Open 8 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

It should be possible to get a mutable reference to a ZST literal A-zst Area: Zero-sized types (ZST). T-types Relevant to the types team, which will review and decide on the PR/issue.
#103821 opened Oct 31, 2022 by joshlf
12
Pointer equality of ZST in debug build is inconsistent with that in release build A-raw-pointers Area: raw pointers, MaybeUninit, NonNull A-zst Area: Zero-sized types (ZST). C-bug Category: This is a bug.
#87477 opened Jul 26, 2021 by danieljl
Documentation of mem::uninitialized potentially confusing for ZSTs A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools A-layout Area: Memory layout of types A-zst Area: Zero-sized types (ZST). C-enhancement Category: An issue proposing an enhancement or a PR with one. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#83995 opened Apr 8, 2021 by steffahn
8
Warn when using [foo; 0] where foo is a non-const expression that evaluates to a Drop type A-const-eval Area: Constant evaluation (MIR interpretation) A-destructors Area: Destructors (`Drop`, …) A-lint Area: Lints (warnings about flaws in source code) such as unused_mut. A-zst Area: Zero-sized types (ZST). T-lang Relevant to the language team, which will review and decide on the PR/issue.
#79580 opened Nov 30, 2020 by bstrie
5
Transmute from one function pointer to another produces "can't transmute zero-sized type" A-diagnostics Area: Messages for errors, warnings, and lints A-raw-pointers Area: raw pointers, MaybeUninit, NonNull A-zst Area: Zero-sized types (ZST). C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#75959 opened Aug 26, 2020 by belkadan
5
RawVec stores a capacity field even if T is zero-sized A-layout Area: Memory layout of types A-specialization Area: Trait impl specialization A-zst Area: Zero-sized types (ZST). C-feature-accepted Category: A feature request that has been accepted pending implementation. I-heavy Issue: Problems and improvements with respect to binary size of generated code. I-slow Issue: Problems and improvements with respect to performance of generated code. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#45431 opened Oct 21, 2017 by gnzlbg
15
Should types that contain zero-length vectors of themselves be allowed? A-array Area: `[T; N]` A-typesystem Area: The type system A-zst Area: Zero-sized types (ZST). C-bug Category: This is a bug. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#11924 opened Jan 30, 2014 by isabelmu
11
ProTip! Updated in the last three days: updated:>2024-10-16.