Skip to content

Unused variables should be reported as warnings #383

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.

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

Closed
pcwalton opened this issue May 17, 2011 · 2 comments
Closed

Unused variables should be reported as warnings #383

pcwalton opened this issue May 17, 2011 · 2 comments
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR) E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@pcwalton
Copy link
Contributor

Title says it all. This could be done in resolve perhaps.

@ghost ghost assigned catamorphism Jun 21, 2011
@catamorphism
Copy link
Contributor

Could be done as part of typestate

@catamorphism
Copy link
Contributor

Added in 4519f54

keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
Add more s390x definitions

This adds more Linux-specific definitions for s390x, to match the
defines provided for other Linux targets.  Many of these will be
required to build std, rustc, and cargo.

In addition, this changes the type of sigaction.sa_flags to "int"
to match current glibc after this bug fix was applied:
https://sourceware.org/bugzilla/show_bug.cgi?id=16713

Some other (cosmetic) changes to bring types in line with the
exact types used in the glibc headers (e.g. ino64_t instead
of ino_t in statfs64).

Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>
kazcw pushed a commit to kazcw/rust that referenced this issue Oct 23, 2018
dlrobertson pushed a commit to dlrobertson/rust that referenced this issue Nov 29, 2018
Move conditional compilation to its own page
ZuseZ4 pushed a commit to EnzymeAD/rust that referenced this issue Mar 7, 2023
calebzulawski added a commit to calebzulawski/rust that referenced this issue Feb 17, 2024
…atch-1

Fix load/store safety comments to require aligned `T`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR) E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

No branches or pull requests

2 participants