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 13 pull requests #31633

Closed
wants to merge 26 commits into from
Closed

Conversation

ketsuban and others added 26 commits February 10, 2016 11:36
The code sections shouldn't be inside a ```text block.
Signed-off-by: NODA, Kai <nodakai@gmail.com>
"destructors" was misspelled.
…ift-documentation, r=steveklabnik

`wrapping_shl` and `wrapping_shr` are easy to mistake for rotations, when in fact they work somewhat differently. The documentation currently available is a little sparse and easy to misinterpret, so I've added a warning to anyone who bumps into them that the equivalent rotate methods may actually be what they're looking for.

If it's deemed useful to add a symmetrical mention to the documentation for the `rotate_left` and `rotate_right` methods, I can certainly have a go at that, but my gut feeling is that people likely to want a rotate will already know about the wrapping-arithmetic methods, for example from writing CPU simulators.
…abnik

The code sections shouldn't be inside a ```text block.

r? @steveklabnik
…klabnik

Just a small documentation change.

It would be great if anyone could check my English.
This is a minor change. Please see title. IMO this is important since this is the first instance when we talk about allocating a vector. Not saying that it is allocated on the stack here leaves room for speculation and this might put off some people (they might not even read the later sections which go into more detail about this).
…veklabnik

Not everyone knows this convention. We could just rename the variables in the
example, but since this notation is commonly used it's a good opportunity to
introduce it.

r? @steveklabnik
I feel sorry for bothering you with such a literally one character changes. If it is counter productive feel free to point it out in the comments, that would be totally understandable. I could try to pack such a changes together in one PR to make them less distractive.

r? @steveklabnik
This PR should make it easier to create a baseline x86 compiler  as well as make cross-compilation possible through a separate set of rlibs.

Plus, a few Linux distributions (e.g. Debian) have voiced interest in having this target available.
@rust-highfive
Copy link
Collaborator

r? @brson

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

@steveklabnik
Copy link
Member Author

@bors: r+ p=1000

@bors
Copy link
Contributor

bors commented Feb 13, 2016

📌 Commit 8895c45 has been approved by steveklabnik

@steveklabnik steveklabnik assigned steveklabnik and unassigned brson Feb 13, 2016
@bors
Copy link
Contributor

bors commented Feb 13, 2016

⌛ Testing commit 8895c45 with merge b7d46ee...

@bors
Copy link
Contributor

bors commented Feb 13, 2016

💔 Test failed - auto-linux-64-nopt-t

@Centril Centril added the rollup A PR which is a rollup label Oct 24, 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.

None yet