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

artifact-app fails to "cargo install" with nightly #47480

Closed
talios opened this issue Jan 16, 2018 · 3 comments
Closed

artifact-app fails to "cargo install" with nightly #47480

talios opened this issue Jan 16, 2018 · 3 comments
Labels
regression-from-stable-to-nightly Performance or correctness regression from stable to nightly. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@talios
Copy link

talios commented Jan 16, 2018

Hi all,

I initially raised this at vitiral/artifact#227 and was redirected to raise as a potential rust-nightly issue.

This is on OSX High Sierra - Installing artifact via cargo +stable install artifact-app works, whereas cargo +nightly install artifact-app fails to build with:

error[E0283]: type annotations required: cannot resolve `std::path::Component<'_>: std::convert::AsRef<_>`
  --> src/utils.rs:40:38
   |
40 |                     remaining.push(a.as_ref());
   |                                      ^^^^^^

error: aborting due to previous error

as the compilation error.

@sfackler
Copy link
Member

Caused by #46985.

@sfackler sfackler added regression-from-stable-to-nightly Performance or correctness regression from stable to nightly. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. labels Jan 16, 2018
@vitiral
Copy link
Contributor

vitiral commented Jan 16, 2018

Thanks @talios

@Mark-Simulacrum
Copy link
Member

Closing in favor of #48716.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression-from-stable-to-nightly Performance or correctness regression from stable to nightly. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

4 participants