Skip to content

[LLVM 4.0] Explicitly call constructor of 'llvm::Error' #38296

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

Merged
merged 1 commit into from
Dec 12, 2016

Conversation

dylanmckay
Copy link
Contributor

The implicit constructor has been deleted. We should use
Error::success() instead.

The constructor in the LLVM headers mentions that "success" should be
used instead of the deleted constructor for clarity.

The implicit constructor has been deleted. We should use
Error::success() instead.

The constructor in the LLVM headers mentions that "success" should be
used instead of the deleted constructor for clarity.
@rust-highfive
Copy link
Contributor

r? @nikomatsakis

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

@dylanmckay
Copy link
Contributor Author

This brings us one step closer to upgrading to LLVM 4.0 in #37609.

@alexcrichton
Copy link
Member

@bors: r+

@bors
Copy link
Collaborator

bors commented Dec 11, 2016

📌 Commit 6222de3 has been approved by alexcrichton

@bors
Copy link
Collaborator

bors commented Dec 12, 2016

⌛ Testing commit 6222de3 with merge 8d66181...

bors added a commit that referenced this pull request Dec 12, 2016
[LLVM 4.0] Explicitly call constructor of 'llvm::Error'

The implicit constructor has been deleted. We should use
Error::success() instead.

The constructor in the LLVM headers mentions that "success" should be
used instead of the deleted constructor for clarity.
@bors bors merged commit 6222de3 into rust-lang:master Dec 12, 2016
@dylanmckay dylanmckay deleted the llvm-4.0-errortype branch February 4, 2017 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants