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.

Sign up for GitHub

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

Jump to bottom

Unstable functionality in Serde #812

Open
5 of 6 tasks
dtolnay opened this issue Mar 9, 2017 · 10 comments
Open
5 of 6 tasks

Unstable functionality in Serde #812

dtolnay opened this issue Mar 9, 2017 · 10 comments
Labels
logistics

Comments

@dtolnay
Copy link
Member

dtolnay commented Mar 9, 2017 •
edited
Loading

Currently unstable


Stabilized


Removed
@nox
Copy link
Contributor

nox commented Apr 23, 2017

Feature zero_one just died. Can we have new versions on both 0.9 and 1.0?

@SimonSapin
Copy link
Contributor

Submitted #898 for zero_one.

@Techcable
Copy link

593bcb0 breaks the unstable feature because you removed the nonzero feature flag which is still required by NonZeroU16 and friends.

@dtolnay
Copy link
Member Author

dtolnay commented May 21, 2018

The nonzero feature flag was removed from nightly in rust-lang/rust#50808.

@Techcable
Copy link

Thanks so much for the clarification, I didn't realize I was using an outdated nightly!

@dtolnay
Copy link
Member Author

dtolnay commented May 27, 2018

I updated the list to reflect functionality that was stabilized in Serde 1.0.60 and 1.0.61. These are no longer behind the "unstable" cfg.

@dtolnay
Copy link
Member Author

dtolnay commented Jun 3, 2018

Added never_type in #1302.

Techcable added a commit to Techcable/serde that referenced this issue Oct 17, 2021
@Techcable
Support std::lazy::OnceCell (unstable: RFC 2788)
81ffba4 
See also serde-rs#812 for other unstable functionality in serde.

Fixes serde-rs#1952
@dtolnay
Copy link
Member Author

dtolnay commented Dec 16, 2022

Added error_in_core in #2344.

@gootorov
Copy link

gootorov commented Jun 22, 2023 •
edited
Loading

Would it be appropriate to add support for Vec<T, A: Allocator>/Box<T, A: Allocator> under the unstable feature flag?
If so, I can submit a PR in some near future.

mina86 added a commit to mina86/serde that referenced this issue Jul 28, 2023
@mina86
Fix unstable build
2edcc81 
Before:

    $ cargo +nightly build --no-default-features --features unstable
       Compiling serde v1.0.177 (/srv/mpn/serde/serde)
    error[E0432]: unresolved import `std_error`
       --> serde/src/de/mod.rs:134:9
    134 | pub use std_error::Error as StdError;
        |         ^^^^^^^^^ maybe a missing crate `std_error`?

After:

    $ cargo +nightly build --no-default-features --features unstable
       Compiling serde v1.0.177 (/srv/mpn/serde/serde)
        Finished dev [unoptimized] target(s) in 1.28s

Note that `unstable` and non-`std` tests are still failing.

Issue: serde-rs#812
@mina86 mina86 mentioned this issue Jul 28, 2023
Closed
mina86 added a commit to mina86/serde that referenced this issue Jul 28, 2023
@mina86
Fix unstable build
dd9fb4e 
Before:

    $ cargo +nightly build --no-default-features --features unstable
       Compiling serde v1.0.177 (/srv/mpn/serde/serde)
    error[E0432]: unresolved import `std_error`
       --> serde/src/de/mod.rs:134:9
    134 | pub use std_error::Error as StdError;
        |         ^^^^^^^^^ maybe a missing crate `std_error`?

After:

    $ cargo +nightly build --no-default-features --features unstable
       Compiling serde v1.0.177 (/srv/mpn/serde/serde)
        Finished dev [unoptimized] target(s) in 1.28s

Note that `unstable` and non-`std` tests are still failing.

Issue: serde-rs#812
@jdygert-spok
Copy link

Error in core has been stabilized. Would it be appropriate to make StdError = core::error::Error when minor >= 81?

@dtolnay dtolnay mentioned this issue Sep 6, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
logistics
Milestone
No milestone
Development

No branches or pull requests
6 participants
@nox @SimonSapin @dtolnay @Techcable @gootorov @jdygert-spok