-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Clean up Box documentation. #24629
Clean up Box documentation. #24629
Conversation
Without the `box` keyword, one of these two reasons is not correct, so let's just eliminate this section and elaborate on the reason for the legit use case inline. Fixes rust-lang#24511
r? @huonw (rust_highfive has picked a reviewer for you, use r? to override) |
//! ``` | ||
//! | ||
//! It wouldn't work. This is because the size of a `List` depends on how many elements are in the | ||
//! list, and so we don't know how much memory to allocate for a `Cons`. By introducing a `Box`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This paragraph lacks curly apostrophes, if you still plan to use those throughout the documentation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes! Interesting, about my editor set up.
I think for now leaving these straight is fine. I've only been doing it in the book thus far, where imho it matters more.
Without the `box` keyword, one of these two reasons is not correct, so let's just eliminate this section and elaborate on the reason for the legit use case inline. Fixes rust-lang#24511
Without the `box` keyword, one of these two reasons is not correct, so let's just eliminate this section and elaborate on the reason for the legit use case inline. Fixes rust-lang#24511
Without the
box
keyword, one of these two reasons is not correct, solet's just eliminate this section and elaborate on the reason for the
legit use case inline.
Fixes #24511