Skip to content

doc: Removing repeated variable name to make it less ambiguious #17456

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
wants to merge 1 commit into from
Closed

doc: Removing repeated variable name to make it less ambiguious #17456

wants to merge 1 commit into from

Conversation

alfiedotwtf
Copy link
Contributor

While reading the intro, I was confused as to why there were two variables named "numbers". Unless I'm mistaken and it's not necessary, let's get rid of it to make it clearer.

@rust-highfive
Copy link
Contributor

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (or someone else) soon.

@steveklabnik
Copy link
Member

I was trying to make it more clear by showing the parts and their combination, but yes, then you have to talk about shadowing. I think this is an improvement. Thanks!

@alfiedotwtf
Copy link
Contributor Author

Hey Steve,

Sorry, I'm new here... I see it passed 3.3, but is failing on LLVM_VERSION=3.4 normal?

@steveklabnik
Copy link
Member

Yes. Travis is just a quick check, bors is the real CI.

@alfiedotwtf
Copy link
Contributor Author

Ahh cool. Thanks :)

bors added a commit that referenced this pull request Sep 23, 2014
While reading the intro, I was confused as to why there were two variables named "numbers". Unless I'm mistaken and it's not necessary, let's get rid of it to make it clearer.
@bors bors closed this Sep 23, 2014
lnicola pushed a commit to lnicola/rust that referenced this pull request Jun 23, 2024
…ng, r=Veykril

Remove panicbit.cargo extension warning

A warning was introduced regarding the incompatabilities between `rust-analyzer` and `panicbit.cargo`'s diagnostics / `cargo check` functionality.

This functionality has been removed in the latest version of the cargo extension (`0.3.0`), which is why the warning can be removed now.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants