Skip to content

Add warning when return is used #594

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

Jump to bottom
Closed
jdm opened this issue Jun 29, 2011 · 2 comments
Closed

Add warning when return is used #594

jdm opened this issue Jun 29, 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

@jdm
Copy link
Contributor

jdm commented Jun 29, 2011

I frequently type return instead of ret, and always end up puzzling over the resulting error for longer than should be necessary. An explicit warning would be nice.
@pcwalton
Copy link
Contributor

At the risk of bikeshedding, maybe we could just make return do the right thing?

@graydon
Copy link
Contributor

graydon commented Feb 14, 2012

Closing as wontfix. We don't detect keywords outside out own keyword set.

@graydon graydon closed this as completed Feb 14, 2012
keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
@bors
Auto merge of rust-lang#594 - PlasmaPower:linux-enoattr, r=alexcrichton
a3e79eb 
Add ENOATTR for Linux

It's defined differently for OSX and *BSD, so having a Linux definition is helpful for cross-platform code.
bors pushed a commit to rust-lang-ci/rust that referenced this issue Oct 26, 2020
@dependabot-preview
Merge pull request rust-lang#594 from bjorn3/dependabot/cargo/bitflag…
137bfd0 
…s-1.1.0
antoyo added a commit to antoyo/rust that referenced this issue Jan 13, 2025
@antoyo
Merge pull request rust-lang#594 from rust-lang/sync_from_rust_2025_0…
59a81c2 
…1_12

Sync from rust 2025/01/12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
3 participants
@graydon @jdm @pcwalton