Conversation
|
r? @huonw (rust_highfive has picked a reviewer for you, use r? to override) |
src/doc/trpl/README.md
Outdated
There was a problem hiding this comment.
s/Higher level/Higher-level/
There was a problem hiding this comment.
nice catch, fixing
54b33a9 to
e9426f7
Compare
src/doc/trpl/README.md
Outdated
There was a problem hiding this comment.
"but eliminate" -> "while eliminating"
There was a problem hiding this comment.
nice catch, thanks
e9426f7 to
d9a78a0
Compare
src/doc/trpl/README.md
Outdated
There was a problem hiding this comment.
Not sure if this line is helpful.
There was a problem hiding this comment.
I think in general I'm a bit more verbose than you are in this. :)
There was a problem hiding this comment.
This one will probably help some readers relax
There was a problem hiding this comment.
The future tense sounds a little weird to me, maybe make it live in now more :P ("copious cross-linking connects these parts together"?)
d9a78a0 to
a0ebd5e
Compare
src/doc/trpl/README.md
Outdated
There was a problem hiding this comment.
I find these extra spaces ugly. Also, it's not what's going to happen in real code, and the differences are visible enough anyways. I'd rather you do this if you want emphasis:
fn main() {
let x = vec![1, 2, 3];
let y = &x[0]; // added
}then
fn main() {
let x = vec![1, 2, 3];
let y = &x[0];
x.push(4); // added
}There was a problem hiding this comment.
it's not what's going to happen in real code
If I were to write this code for real, I would put those spaces there. The principle is 'coding in paragraphs', each separate thing gets a newline. In more real code, there might be two or three things between each space, but I find your version to be quite cramped.
a0ebd5e to
db058f8
Compare
src/doc/trpl/README.md
Outdated
There was a problem hiding this comment.
Is this code example really worth the space in the brief intro? This seems like a case when space is at a premium and we want to make it as "tight" as reasonable. It seems to me that the paragraph above is probably all that's needed, or even reduced further with some cross-links to more explanations (Rust is statically typed but has type inference, so type annotations are [optional](...)).
|
(All my comments are meant to be discussion starters, I'm not rabidly in favour of any of them, just wondering if we could |
2be0873 to
90d6965
Compare
90d6965 to
bf88539
Compare
|
I want to land this so that it gets into the nightly tonight. If there's any more nits, please open an issue and I'll just take care of it, but I don't want to have another day with the intro being just straight-up wrong. :) |
|
@bors: r+ rollup |
|
📌 Commit bf88539 has been approved by |
…labnik Now that the new TOC has landed, I've started doing an editing pass to get the old content into the right shape. I felt this introduction was significant enough to send as its own PR, though, as it's the introduction. It's possible that we may just want to replace 'the intro' with this directly, but this PR doesn't do that.
…labnik Now that the new TOC has landed, I've started doing an editing pass to get the old content into the right shape. I felt this introduction was significant enough to send as its own PR, though, as it's the introduction. It's possible that we may just want to replace 'the intro' with this directly, but this PR doesn't do that.
|
|
||
| let y = x[0].clone(); | ||
|
|
||
| x.push(4); |
There was a problem hiding this comment.
Why push an integer to a vector of &str?
…labnik Now that the new TOC has landed, I've started doing an editing pass to get the old content into the right shape. I felt this introduction was significant enough to send as its own PR, though, as it's the introduction. It's possible that we may just want to replace 'the intro' with this directly, but this PR doesn't do that.
…labnik Now that the new TOC has landed, I've started doing an editing pass to get the old content into the right shape. I felt this introduction was significant enough to send as its own PR, though, as it's the introduction. It's possible that we may just want to replace 'the intro' with this directly, but this PR doesn't do that.
…labnik Now that the new TOC has landed, I've started doing an editing pass to get the old content into the right shape. I felt this introduction was significant enough to send as its own PR, though, as it's the introduction. It's possible that we may just want to replace 'the intro' with this directly, but this PR doesn't do that.
…labnik Now that the new TOC has landed, I've started doing an editing pass to get the old content into the right shape. I felt this introduction was significant enough to send as its own PR, though, as it's the introduction. It's possible that we may just want to replace 'the intro' with this directly, but this PR doesn't do that.
…labnik Now that the new TOC has landed, I've started doing an editing pass to get the old content into the right shape. I felt this introduction was significant enough to send as its own PR, though, as it's the introduction. It's possible that we may just want to replace 'the intro' with this directly, but this PR doesn't do that.
…labnik Now that the new TOC has landed, I've started doing an editing pass to get the old content into the right shape. I felt this introduction was significant enough to send as its own PR, though, as it's the introduction. It's possible that we may just want to replace 'the intro' with this directly, but this PR doesn't do that.
…labnik Now that the new TOC has landed, I've started doing an editing pass to get the old content into the right shape. I felt this introduction was significant enough to send as its own PR, though, as it's the introduction. It's possible that we may just want to replace 'the intro' with this directly, but this PR doesn't do that.
…labnik Now that the new TOC has landed, I've started doing an editing pass to get the old content into the right shape. I felt this introduction was significant enough to send as its own PR, though, as it's the introduction. It's possible that we may just want to replace 'the intro' with this directly, but this PR doesn't do that.
|
Needs 0a2885a |
Now that the new TOC has landed, I've started doing an editing pass to get the old content into the right shape. I felt this introduction was significant enough to send as its own PR, though, as it's the introduction.
It's possible that we may just want to replace 'the intro' with this directly, but this PR doesn't do that.