Skip to content
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

doc: Missing link in language design FAQ #14914

Closed
graue opened this issue Jun 15, 2014 · 1 comment
Closed

doc: Missing link in language design FAQ #14914

graue opened this issue Jun 15, 2014 · 1 comment

Comments

@graue
Copy link

graue commented Jun 15, 2014

Section 1.7 of the language design FAQ, "No guaranteed tail-call optimization", appears to be missing a link, between the words "see" and "for":

see for a detailed explanation with references

@cmr, what's meant to go here?
@emberian
Copy link
Member

https://mail.mozilla.org/pipermail/rust-dev/2013-April/003557.html

alexcrichton added a commit to alexcrichton/rust that referenced this issue Jun 16, 2014
@alexcrichton
doc: Fix a link in the FAQ
5d44a1c 
Closes rust-lang#14914
@alexcrichton alexcrichton mentioned this issue Jun 16, 2014
Closed
bors added a commit to rust-lang-ci/rust that referenced this issue Jun 5, 2023
@bors
Auto merge of rust-lang#14914 - mashuler:fix-rustup-installation-desc…
f6e3a87 
…ription, r=lnicola

Fix rustup installation description

While going through the process of installing rust-analyzer to use with Neovim, I noticed that the instructions for installing with rustup are incorrect now that [issue rust-lang#2411](rust-lang/rustup#2411) has been closed. Now when rust-analyzer is installed using rustup, it is installed in ~/.cargo/bin and a symlink or some other workaround is no longer needed. I have updated the documentation accordingly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

doc: Fix a link in the FAQ alexcrichton/rust
2 participants
@emberian @graue