Skip to content

Conversation

@tshepang
Copy link
Member

No description provided.

@rust-highfive
Copy link
Contributor

r? @huonw

(rust_highfive has picked a reviewer for you, use r? to override)

@huonw
Copy link
Contributor

huonw commented Jul 25, 2015

I think the phrase is talking about the "the", not the "Rust".

@tshepang tshepang closed this Jul 25, 2015
@tshepang tshepang reopened this Jul 25, 2015
@tshepang
Copy link
Member Author

(closed by mistake)

@tshepang
Copy link
Member Author

@huonw That's not clear, and the qualifier is not even needed anyways. It should be obvious that we are talking about the Rust compiler.

@leoyvens
Copy link
Contributor

I don't think it's obvious. The only implementation is a compiler immediately makes the reader ask: "what compiler?"

@tshepang
Copy link
Member Author

@leodasvacas the are 2 things presented: interpreter and compiler. There is then a claim that the only implementation that exists (at the moment) is a compiler... i.e. there is no interpreter.

Given this is the Rust reference, if one were to mention some other compiler, it would be qualified (e.g. the C++ compiler).

@leoyvens
Copy link
Contributor

Saying "the C++ compiler" would be unclear, there is no "the C++ compiler" but there are clang and gcc. In the case of rust, we have a compiler which is called "the Rust compiler", rather than "the Rust-o-tron3000". It's good to have precise definitions in a language reference, even if they seem obvious.

@tshepang
Copy link
Member Author

@leodasvacas Do you suggest that all instances of "the compiler" should be replaced with "the Rust compiler"?

@tshepang
Copy link
Member Author

@leodasvacas The phrase "C++ compiler" is valid in cases where the implementation doesn't matter... there is stuff that is common among all implementations.

@steveklabnik
Copy link
Contributor

After leaving this sit for a while, I think we'll just keep it as it is. Thanks though!

@tshepang
Copy link
Member Author

@steveklabnik if this PR is not good enough to be merged, one that should is one that replaces all occurrences of the compiler with the Rust compiler. Else, we are leaving this inaccurate statement alive:

...from now on referred to as the Rust compiler...

@steveklabnik
Copy link
Contributor

steveklabnik commented Sep 28, 2015 via email

@tshepang
Copy link
Member Author

you may

@tshepang tshepang deleted the claim-not-accurate branch September 28, 2015 15:47
@steveklabnik
Copy link
Contributor

So, thinking about it more, I actually do prefer this change. It looks like you deleted the branch, though, so I can't re-open. Can you?

@tshepang tshepang restored the claim-not-accurate branch September 29, 2015 09:59
@tshepang
Copy link
Member Author

I undeleted it. Thanks for re-considering it.

@steveklabnik
Copy link
Contributor

@bors: r+ rollup

@steveklabnik
Copy link
Contributor

No problem, and thanks for being patient. I originally thought this came much, much earlier in the reference.

@tshepang
Copy link
Member Author

you'll need to re-open the issue as well

@steveklabnik steveklabnik reopened this Sep 29, 2015
@steveklabnik
Copy link
Contributor

Ugh, I thought I did. thanks

@steveklabnik
Copy link
Contributor

@bors: r+ rollup

@bors
Copy link
Collaborator

bors commented Sep 29, 2015

📌 Commit 36582da has been approved by steveklabnik

@bors
Copy link
Collaborator

bors commented Sep 29, 2015

⌛ Testing commit 36582da with merge 5f06607...

@tshepang
Copy link
Member Author

yay!

@bors bors merged commit 36582da into rust-lang:master Sep 29, 2015
@tshepang tshepang deleted the claim-not-accurate branch September 30, 2015 05:00
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.

6 participants