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

Stabilize dyn trait #49968

Merged
merged 9 commits into from
Apr 27, 2018
Merged

Stabilize dyn trait #49968

merged 9 commits into from
Apr 27, 2018

Conversation

pvdrz
Copy link
Contributor

@pvdrz pvdrz commented Apr 14, 2018

This PR stabilizes RFC 2113. I followed the stabilization guide.

Related issue: #49218

@rust-highfive
Copy link
Collaborator

r? @nikomatsakis

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

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Apr 14, 2018
@bors
Copy link
Contributor

bors commented Apr 16, 2018

☔ The latest upstream changes (presumably #50003) made this pull request unmergeable. Please resolve the merge conflicts.

@rust-highfive
Copy link
Collaborator

Your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

Click to expand the log.
[00:00:47] configure: rust.quiet-tests     := True
---
[00:34:35] error: this feature has been stable since 1.27.0. Attribute no longer needed
[00:34:35]   --> librustdoc/lib.rs:26:12
[00:34:35]    |
[00:34:35] 26 | #![feature(dyn_trait)]
---
[00:34:36] Makefile:28: recipe for target 'all' failed
[00:34:36] make: *** [all] Error 1

I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact @TimNN. (Feature Requests)

@bors
Copy link
Contributor

bors commented Apr 22, 2018

☔ The latest upstream changes (presumably #50121) made this pull request unmergeable. Please resolve the merge conflicts.

@rust-highfive
Copy link
Collaborator

The job x86_64-gnu-llvm-3.9 of your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

Click to expand the log.
[00:46:39] ....................................................................................................
[00:46:43] ....................................................................................................
[00:46:48] ....................................................................................................
[00:46:53] ....................................................................................................
[00:47:00] ..............................................F.....................................................
[00:47:14] ....................................................................................................
[00:47:22] ..............................i.....................................................................
[00:47:28] ......i.............................................................................................
[00:47:35] ......................ii............................................................................

I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact @TimNN. (Feature Requests)

@nikomatsakis
Copy link
Contributor

@TimNN btw that message doesn't seem to include the error =)

@pvdrz
Copy link
Contributor Author

pvdrz commented Apr 25, 2018

I'm having trouble with llvm, I'm going to rebuild everything from scratch

@pvdrz
Copy link
Contributor Author

pvdrz commented Apr 25, 2018

@nikomatsakis I think we are ready

@nikomatsakis
Copy link
Contributor

r=me once travis is happy

@nikomatsakis
Copy link
Contributor

@bors r+

@bors
Copy link
Contributor

bors commented Apr 25, 2018

📌 Commit 3b34dbf has been approved by nikomatsakis

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Apr 25, 2018
@rust-highfive
Copy link
Collaborator

The job mingw-check of your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

Click to expand the log.
[00:00:56] configure: llvm.assertions      := True
[00:00:56] configure: build.locked-deps    := True
[00:00:56] configure: llvm.ccache          := sccache
[00:00:56] configure: build.openssl-static := True
[00:00:56] configure: build.configure-args := ['--enable-quiet-tests', '--enable-sccache', ' ...
[00:00:56] configure: writing `config.toml` in current directory
[00:00:56] configure: 
[00:00:56] configure: run `python /checkout/x.py --help`
[00:00:56] configure: 
---
[00:07:27]    Compiling rand v0.4.2
[00:07:27]    Compiling remove_dir_all v0.5.1
[00:07:28]    Compiling tempdir v0.3.7
[00:07:28]    Compiling rustdoc v0.0.0 (file:///checkout/src/librustdoc)
[00:07:29] error[E0658]: `dyn Trait` syntax is unstable (see issue #44662)
[00:07:29]     |
[00:07:29]     |
[00:07:29] 166 |     let emitter: Box<dyn Emitter + sync::Send> = match error_format {
[00:07:29]     |
[00:07:29]     |
[00:07:29]     = help: add #![feature(dyn_trait)] to the crate attributes to enable
[00:07:29] error: aborting due to previous error
[00:07:29] 
[00:07:29] For more information about this error, try `rustc --explain E0658`.
[00:07:29] error: Could not compile `rustdoc`.
[00:07:29] error: Could not compile `rustdoc`.
[00:07:29] 
[00:07:29] Caused by:
[00:07:29]   process didn't exit successfully: `/checkout/obj/build/bootstrap/debug/rustc --crate-name rustdoc librustdoc/lib.rs --color always --error-format json --crate-type lib --emit=dep-info,metadata -C debug-assertions=off -C overflow-checks=on -C metadata=53bc6cad8d025cf8 -C extra-filename=-53bc6cad8d025cf8 --out-dir /checkout/obj/build/x86_64-unknown-linux-gnu/stage0-tools/i686-pc-windows-gnu/release/deps --target i686-pc-windows-gnu -C incremental=/checkout/obj/build/x86_64-unknown-linux-gnu/stage0-tools/i686-pc-windows-gnu/release/incremental -L dependency=/checkout/obj/build/x86_64-unknown-linux-gnu/stage0-tools/i686-pc-windows-gnu/release/deps -L dependency=/checkout/obj/build/x86_64-unknown-linux-gnu/stage0-tools/release/deps --extern pulldown_cmark=/checkout/obj/build/x86_64-unknown-linux-gnu/stage0-tools/i686-pc-windows-gnu/release/deps/libpulldown_cmark-8f75380f3365e775.rmeta --extern tempdir=/checkout/obj/build/x86_64-unknown-linux-gnu/stage0-tools/i686-pc-windows-gnu/release/deps/libtempdir-4d964115e60069d9.rmeta -L native=/cargo/registry/src/github.com-1ecc6299db9ec823/winapi-i686-pc-windows-gnu-0.4.0/lib` (exit code: 101)
[00:07:29] command did not execute successfully: "/checkout/obj/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "check" "--target" "i686-pc-windows-gnu" "-j" "4" "--release" "--locked" "--color" "always" "--manifest-path" "/checkout/src/tools/rustdoc/Cargo.toml" "--message-format" "json"
[00:07:29] expected success, got: exit code: 101
[00:07:29] thread 'main' panicked at 'cargo must succeed', bootstrap/compile.rs:1091:9
[00:07:29] travis_fold:end:stage0-rustdoc

[00:07:29] travis_time:end:stage0-rustdoc:start=1524673242704764431,finish=1524673251062949500,duration=8358185069

I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact @TimNN. (Feature Requests)

@nikomatsakis
Copy link
Contributor

@bors r- -- travis

@bors bors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Apr 25, 2018
@nikomatsakis
Copy link
Contributor

@bors r+

@bors
Copy link
Contributor

bors commented Apr 25, 2018

📌 Commit 545f5f5 has been approved by nikomatsakis

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Apr 25, 2018
@pietroalbini pietroalbini added the relnotes Marks issues that should be documented in the release notes of the next release. label Apr 27, 2018
@bors
Copy link
Contributor

bors commented Apr 27, 2018

⌛ Testing commit 545f5f5574a06896611508ad4406b97702b5d081 with merge 5264567ea97ef1cb749cf53543dfcf1c99d1fa7c...

@bors
Copy link
Contributor

bors commented Apr 27, 2018

💔 Test failed - status-travis

@rust-highfive

This comment has been minimized.

@bors bors removed the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Apr 27, 2018
@rust-highfive

This comment has been minimized.

@kennytm kennytm added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Apr 27, 2018
@pvdrz
Copy link
Contributor Author

pvdrz commented Apr 27, 2018

@nikomatsakis I think it's ready

@kennytm
Copy link
Member

kennytm commented Apr 27, 2018

@bors r=nikomatsakis

@bors
Copy link
Contributor

bors commented Apr 27, 2018

📌 Commit b5c7cbf has been approved by nikomatsakis

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Apr 27, 2018
kennytm added a commit to kennytm/rust that referenced this pull request Apr 27, 2018
…komatsakis

Stabilize dyn trait

This PR stabilizes RFC 2113. I followed the [stabilization guide](https://forge.rust-lang.org/stabilization-guide.html).

Related issue: rust-lang#49218
bors added a commit that referenced this pull request Apr 27, 2018
Rollup of 9 pull requests

Successful merges:

 - #49858 (std: Mark `ptr::Unique` with `#[doc(hidden)]`)
 - #49968 (Stabilize dyn trait)
 - #50192 (Add some utilities to `libsyntax`)
 - #50251 (rustc: Disable threads in LLD for wasm)
 - #50263 (rustc: Emit `uwtable` for allocator shims)
 - #50269 (Update `parking_lot` dependencies)
 - #50273 (Allow #[inline] on closures)
 - #50284 (fix search load page failure)
 - #50257 (Don't ICE on tuple struct ctor with incorrect arg count)

Failed merges:
@bors bors merged commit b5c7cbf into rust-lang:master Apr 27, 2018
@pvdrz pvdrz deleted the stabilize_dyn branch May 2, 2018 03:40
@alercah
Copy link
Contributor

alercah commented May 3, 2018

Not sure if this is the best place to ask, but in the future, when a sub-feature is split off for separate stabilization, can we please ensure that docs PRs are filed for the sub-feature as a prerequisite? We have rust-lang/reference#279 for dyn Trait, but looking at the tracking issue #44662, it looks like it isn't stabilized, so it would otherwise slip through the cracks until the full feature was done. (cc @Havvy)

@steveklabnik
Copy link
Member

steveklabnik commented May 3, 2018

@alercah for the stuff relating to the edition, we relaxed the requirement to "file an issue". I made issues for everything in RBE and the book, but I thought yinz were handling the reference your own way. If it's easier, you all may want to copy over https://github.com/rust-lang/book/issues?q=is%3Aopen+is%3Aissue+label%3A%22Blocking+Rust+2018%22, or I'm happy to do it too, whatever works for you all.

that being said, yeah, when stuff gets split off, commenting in those issues about it would be 👍

@alercah
Copy link
Contributor

alercah commented May 3, 2018

Oops sorry, yes, I meant issues, not PRs. @matthewjasper filed a number of issues for the reference for Rust 2018 features, and that's good, but there are always going to be stabilizations that aren't planned out like that. So the point that I was trying to make subtly, and apparently failed at because I mixed things up, was that I think that at some point someone should have asked "Do necessary issues exist on docs repositories?" before this got merged. It's not clear to me that it wasn't because we already have one for dyn Trait writ large, in which case it just slipped through, or that it's because nobody checked.

As a side note, the stabilization guide needs updating, which would probably reduce the likelihood of future miscommunication.

@steveklabnik
Copy link
Member

I think that at some point someone should have asked "Do necessary issues exist on docs repositories?" before this got merged.

yes please! Agree 1000%.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
relnotes Marks issues that should be documented in the release notes of the next release. 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.

8 participants