Skip to content

Remove be #2227

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
brson opened this issue Apr 17, 2012 · 4 comments
Closed

Remove be #2227

brson opened this issue Apr 17, 2012 · 4 comments
Labels
A-codegen Area: Code generation A-grammar Area: The grammar of Rust A-type-system Area: Type system E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@brson
Copy link
Contributor

brson commented Apr 17, 2012

It's currently just a rarely tested synonym for ret. Regardless of whether we eventually decide to implement tail calls, be is not doing anything for us today.

Don't forget to remove it from the manual too.
@graydon
Copy link
Contributor

graydon commented Apr 17, 2012

Not presently, but it's necessary to differentiate tail-call from non. So this is blocked on whether-we-keep-tailcalls.

@brson
Copy link
Contributor Author

brson commented Apr 17, 2012

I'm suggesting we unblock it and just remove the keyword since the tail call decision seems like it's going to be pushed back forever. We could leave be a reserved word as insurance. Either way it's not a big deal since there's so little code dedicated to be.

@catamorphism
Copy link
Contributor

I agree with @brson . Bit-rotted code is not good. We can always reintroduce it later.

@graydon
Copy link
Contributor

graydon commented Apr 20, 2012

ok

@ghost ghost assigned lkuper May 14, 2012
@lkuper lkuper closed this as completed May 15, 2012
lkuper added a commit to lkuper/rust that referenced this issue May 15, 2012
@lkuper
Remove be keyword.
b8880e3 
Closes rust-lang#2227.
@kennytm kennytm mentioned this issue Jan 15, 2015
Closed
bors added a commit to rust-lang-ci/rust that referenced this issue Sep 22, 2022
@bors
Auto merge of rust-lang#2227 - RalfJung:doc, r=RalfJung
ada7b72 
make some rustdoc comments more readable
celinval added a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
@celinval @adpaco-aws
Fix infinite loop on stub resolution and improve error handling (rust…
07a48e6 
…-lang#2227)

Refactor the name resolution code to take into consideration loops added by loops in globs. Since I had to do some refactoring, I also ensured we now the reason why the resolution failed and print it as part of the error.

Co-authored-by: Adrian Palacios <73246657+adpaco-aws@users.noreply.github.com>
BoxyUwU pushed a commit to BoxyUwU/rust that referenced this issue Jan 29, 2025
@jieyouxu
Merge pull request rust-lang#2227 from Joren-vanGoethem/master
bec4359
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-codegen Area: Code generation A-grammar Area: The grammar of Rust A-type-system Area: Type system 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
4 participants
@graydon @brson @catamorphism @lkuper