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 8 pull requests #65196

Merged
merged 30 commits into from
Oct 8, 2019
Merged

Rollup of 8 pull requests #65196

merged 30 commits into from
Oct 8, 2019

Conversation

Centril
Copy link
Contributor

@Centril Centril commented Oct 8, 2019

Successful merges:

Failed merges:

r? @ghost

sinkuu and others added 30 commits October 3, 2019 15:24
To make `new` method appear first in documentation.
Change-Id: I0c5c4d767be2647e6f017ae7bf83558c56dbca97
Change-Id: I0c5c4d767be2647e6f017ae7bf83558c56dbca97
Change-Id: I0c5c4d767be2647e6f017ae7bf83558c56dbca97
Didn't find any bugs here, but you really don't want these to fall out
of sync.
Existing code could overlook types/substitutions that are
embedded in (e.g.) an unevaluated constant.
In such a case, the `Infer` is converted to a `Bound`
Also, make `-Zverbose` dump all info about constants.
…uppe

rewrite documentation for unimplemented! to clarify use

The current docs for `unimplemented!` seem to miss the point of this macro.

> This can be useful if you are prototyping and are just looking to have your code type-check, or if you're implementing a trait that requires multiple methods, and you're only planning on using one of them.

You could also return a `()` if you just want your code to type-check.

I think `unimplemented!` is useful for when you want your program to exit when it reaches an unimplemented area.

I rewrote the explanation and gave examples of both forms of this macro that I think clarify its use a little better.
syntax: more cleanups in item and function signature parsing

Follow up to rust-lang#64910.

Best read commit-by-commit.

r? @estebank
Make `Cell::new` method come first in documentation

Methods to create a thing usually comes first in `std` documentation, and `Cell` has been an exception. Also, `T: Copy` specialized methods should not be on top of the page. (This had led me to miss that most of its methods are not bounded by `Copy`...)
…-E0561, r=Centril

Add long error explanation for E0561

Part of rust-lang#61137
Suggest dereferencing boolean reference when used in 'if' or 'while'

Implements rust-lang#64557
…arkor

Fix const generic arguments not displaying in types mismatch diagnostic

Fixes rust-lang#61395
…ush-1, r=varkor

fix bug in folding for constants

These was a bug in the folding for constants that caused it to overlook bound regions. This branch includes some other little things that I did while trying to track the bug down.

r? @oli-obk
…kruppe

use 'invalid argument' for vxWorks

vxWorks is using "invalid argument" instead of "Invalid argument" in reporting invalid options

r? @rkruppe
@Centril
Copy link
Contributor Author

Centril commented Oct 8, 2019

@bors r+ p=8 rollup=never

@bors
Copy link
Contributor

bors commented Oct 8, 2019

📌 Commit bc7df81 has been approved by Centril

@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Oct 8, 2019
@bors
Copy link
Contributor

bors commented Oct 8, 2019

⌛ Testing commit bc7df81 with merge 1e1f25e...

bors added a commit that referenced this pull request Oct 8, 2019
Rollup of 8 pull requests

Successful merges:

 - #64726 (rewrite documentation for unimplemented! to clarify use)
 - #65040 (syntax: more cleanups in item and function signature parsing)
 - #65046 (Make `Cell::new` method come first in documentation)
 - #65098 (Add long error explanation for E0561)
 - #65150 (Suggest dereferencing boolean reference when used in 'if' or 'while')
 - #65154 (Fix const generic arguments not displaying in types mismatch diagnostic)
 - #65181 (fix bug in folding for constants)
 - #65187 (use 'invalid argument' for vxWorks)

Failed merges:

 - #65179 (Add long error explanation for E0567)

r? @ghost
@Centril Centril added the rollup A PR which is a rollup label Oct 8, 2019
@bors
Copy link
Contributor

bors commented Oct 8, 2019

☀️ Test successful - checks-azure
Approved by: Centril
Pushing 1e1f25e to master...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants