Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Proper tail calls #1888

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

Closed
wants to merge 8 commits into from
Closed

Proper tail calls #1888

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
f1d3282
RFC for proper tail calls
DemiMarie Feb 7, 2017
7fbf2c1
Provide link to implementation
DemiMarie Feb 7, 2017
55e4056
Add feature name
DemiMarie Feb 7, 2017
7f9fb23
typo: varient is spelled variant
DemiMarie Feb 7, 2017
c7b83dc
Create a new file with RFC instead of changing template
DemiMarie Feb 8, 2017
788fd7e
Add license
DemiMarie Feb 8, 2017
1e7d448
Fix 404 link in RFC
jmcomets Feb 10, 2017
79d936f
Merge pull request #1 from jmcomets/patch-1
DemiMarie Feb 11, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add license
  • Loading branch information
@DemiMarie
DemiMarie committed Feb 8, 2017
commit 788fd7e25b9948a7615672df4bff2f904a711cc0
5 changes: 5 additions & 0 deletions 0000-proper-tail-calls.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,3 +165,8 @@ continue to do so if this RFC is not accepted.
Is there a way to emulate proper tail calls when compiling to targets that don't
support them? Is it possible to eliminate the overhead imposed on every
non-tail call?

# License of this RFC
[license]: #license

This RFC is licensed under the same terms as Rust itself.