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 11 pull requests #36012

Closed
wants to merge 26 commits into from
Closed

Conversation

Stebalien and others added 26 commits August 20, 2016 15:20
Doing otherwise would break traits like `ToString`.
This pull request adds a module-level example of how all the range operators work. It also slims down struct-level examples in lieu of a link to module examples.

add feature for inclusive_range_syntax

fix incorrectly closed code fences
They're the same thing but it's better to keep the terminology consistent.
PR rust-lang#35695 for `Range` was approved, so it seems that this side-effect-free style is preferred for Range* examples. This PR performs the same translation for `RangeFrom` and `RangeInclusive`. It also removes what looks to be an erroneously commented line for `#![feature(step_by)]`, and an unnecessary primitive-type annotation in `0u8..`.

add `fn main` wrappers to enable Rust Playground "Run" button
r? @steveklabnik

add examples that lift `<<` and `>>` to a trivial struct

replace `Scalar` structs with struct tuples

add `fn main` wrappers to enable Rust Playground "Run" button
The affected API apparently had changed with commit d59accf.
Fixes rust-lang#35966.

Signed-off-by: Johannes Löthberg <johannes@kyriasis.com>
…tln-remaining, r=GuillaumeGomez

accumulate vector and assert for RangeFrom and RangeInclusive examples

PR rust-lang#35695 for `Range` was merged, so it seems that this side-effect-free style is preferred for Range* examples. This PR performs the same translation for `RangeFrom` and `RangeInclusive`. It also removes what looks to be an erroneously commented line for `#![feature(step_by)]`, and an unnecessary primitive-type annotation in `0u8..`.
…les, r=steveklabnik

refactor range examples

This pull request adds a module-level example of how all the range operators work. It also slims down struct-level examples in lieu of a link to module examples.
Clarify/fix formatting docs concerning fmt::Result/fmt::Error

1. `fmt::Result` != `io::Result<()>`
2. Formatters should only propagate errors, not return their own.

Confusion on reddit: https://www.reddit.com/r/rust/comments/4yorxr/is_implt_tostring_for_t_where_t_display_sized_a/
…klabnik

add evocative examples for `Shl` and `Shr`

r? @steveklabnik
…klabnik

add links to interesting items in `std::ptr` documentation

r? @steveklabnik
…steveklabnik

Updated code sample in chapter on syntax extensions.

The affected API apparently had changed with commit d59accf.

---

Further more I had to add

```toml
[lib]
name = "roman_numerals"
crate-type = ["dylib"]
```

to `Cargo.toml` as I otherwise got this compiler error (despite `#![crate_type="dylib"]`):

    [E0457]: plugin `roman_numerals` only found in rlib format, but must be available in dylib format

Might be worth adding a note about that?
Rename {int,uint} methods to {isize,usize}.

None
…le, r=GuillaumeGomez

add a simple example for `thread::current()`

r? @GuillaumeGomez
@rust-highfive
Copy link
Collaborator

r? @aturon

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

@steveklabnik
Copy link
Member Author

@bors: r+ p=1

@bors
Copy link
Contributor

bors commented Aug 26, 2016

📌 Commit 92e0528 has been approved by steveklabnik

@bors
Copy link
Contributor

bors commented Aug 26, 2016

⌛ Testing commit 92e0528 with merge 72aa1a0...

@bors
Copy link
Contributor

bors commented Aug 26, 2016

💔 Test failed - auto-win-msvc-64-opt-rustbuild

@sophiajt
Copy link
Contributor

@bors retry

@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.