-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Can't ignore soft destabilization of rustc-serialize
with #![allow(soft_unstable)]
#123156
Comments
rustc-serialize
with #![feature(libstd_sys_internals)]
rustc-serialize
with #![allow(soft_unstable)]
The derived |
WG-prioritization assigning priority (Zulip discussion). @rustbot label -I-prioritize +P-critical |
cc @jhpratt |
I'm actually not sure this is a T-libs issue. I suspect it's related to |
I have confirmed this is an issue with the expansion of @rustbot claim |
PR is up, including a regression test: #123182 |
Rollup merge of rust-lang#123182 - jhpratt:fix-decodable-derive, r=davidtwco Avoid expanding to unstable internal method Fixes rust-lang#123156 Rather than expanding to `std::rt::begin_panic`, the expansion is now to `unreachable!()`. The resulting behavior is identical. A test that previously triggered the same error as rust-lang#123156 has been added to ensure it does not regress. r? compiler
In chrono we have support for
rustc-serialize
behind a feature flag.As a workaround for #116016 I added the line:
#![cfg_attr(feature = "rustc-serialize", allow(deprecated), allow(soft_unstable))]
It now gives a new error:
cc @jhpratt
The text was updated successfully, but these errors were encountered: