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.

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

Rollup of 14 pull requests #24648

Merged
merged 40 commits into from
Apr 21, 2015
Merged

Rollup of 14 pull requests #24648

merged 40 commits into from
Apr 21, 2015

Conversation

krzysz00 and others added 30 commits April 16, 2015 21:34
As far as I can tell, this conversion to integer to floating point does not need to happen and is beside the point
Now that we're not doing the guessing game, a lot of this is irrelevant.
We want to talk about how to pattern match on structs, so let's bump
it back one.
It's a trait implementation, so we need traits first.
It's a language feature, so it belongs here.
Let's talk about generics first, since we use traits to bound them
in funtions.

Partially addresses rust-lang#24325

Fixes rust-lang#24271
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
Due to documenting `transmute`, addresses part of rust-lang#12905
The slice patterns example was nice, so let's put it with the other
slice pattern feature gate documentation.

Fixes rust-lang#24573
Many unsafe features are now in the unstable section, so this section is
really just about raw pointers now. That also makes sense for its place
in the TOC.

This addresses part of rust-lang#12905.
and while let
…=alexcrichton

When `liballoc` is compiled with `--cfg feature=\"external_features\"`, several `improper_ctypes` warnings are generated. Since these warnings are harmless, I have added a directive to suppress them.
A bunch of chapters, fixes an issue or two as well.

r? @alexcrichton
As far as I can tell, this conversion to integer to floating point does not need to happen and is beside the point
Fixes rust-lang#24173 

These docs could all use examples, so for now, let's just remove the bad one, and when I go over this whole module I'll put in better ones.
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
…ichton

Many unsafe features are now in the unstable section, so this section is
really just about raw pointers now. That also makes sense for its place
in the TOC.

This addresses part of rust-lang#12905.
…richton

Due to documenting `transmute`, addresses part of rust-lang#12905
@rust-highfive
Copy link
Collaborator

r? @huonw

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

@steveklabnik steveklabnik assigned steveklabnik and unassigned huonw Apr 21, 2015
@steveklabnik
Copy link
Member Author

Fixed up #24640 so it gets in too.

@steveklabnik
Copy link
Member Author

@bors: r+ p=100 force

@bors
Copy link
Contributor

bors commented Apr 21, 2015

📌 Commit 9ddcc38 has been approved by steveklabnik

@bors
Copy link
Contributor

bors commented Apr 21, 2015

⌛ Testing commit 9ddcc38 with merge 21c48c3...

bors added a commit that referenced this pull request Apr 21, 2015
@bors bors merged commit 9ddcc38 into rust-lang:master Apr 21, 2015
@Centril Centril added the rollup A PR which is a rollup label Oct 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rollup A PR which is a rollup
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants