-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
syntax: remove abi::Os and abi::Architecture #39218
Conversation
They're long dead since the switch to flexible targets, but was not removed like their consumers were. Interesting they even got maintained by various porters out there! Technically [syntax-breaking] as they're public API, but since they're unused in the compiler, the potential breakage IMO should be minimal.
(rust_highfive has picked a reviewer for you, use r? to override) |
@bors: r+ Thanks! |
📌 Commit 578001a has been approved by |
⌛ Testing commit 578001a with merge a9c7475... |
💔 Test failed - status-appveyor |
Test failure spurious -- EDIT: #33434 |
⌛ Testing commit 578001a with merge 78c43f6... |
💔 Test failed - status-travis |
… On Sat, Jan 21, 2017 at 11:50 AM, bors ***@***.***> wrote:
💔 Test failed - status-travis
<https://travis-ci.org/rust-lang/rust/builds/194064876>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#39218 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95KVqPFok9MCZM7mhG7dcQ8eixIP2ks5rUmGBgaJpZM4LqAvd>
.
|
syntax: remove abi::Os and abi::Architecture They're long dead since the switch to flexible targets, but was not removed like their consumers were. Interesting they even got maintained by various porters out there! Technically [syntax-breaking] as they're public API, but since they're unused in the compiler, the potential breakage IMO should be minimal.
☀️ Test successful - status-appveyor, status-travis |
They're long dead since the switch to flexible targets, but was not removed like their consumers were. Interesting they even got maintained by various porters out there!
Technically [syntax-breaking] as they're public API, but since they're unused in the compiler, the potential breakage IMO should be minimal.