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

Tracking Issue for deriving Default on enums #86985

Closed
1 of 3 tasks
jhpratt opened this issue Jul 8, 2021 · 1 comment
Closed
1 of 3 tasks

Tracking Issue for deriving Default on enums #86985

jhpratt opened this issue Jul 8, 2021 · 1 comment
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@jhpratt
Copy link
Member

jhpratt commented Jul 8, 2021

This is a tracking issue for the RFC 3107.
The feature gate for the issue is #![feature(derive_default_enum)].

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps

Unresolved Questions

  • Should multiple #[default] attributes on the same variant be denied?

Implementation history

Initial implementation in #86735, which includes the feature gate and necessary errors.

@jhpratt jhpratt added the C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC label Jul 8, 2021
@rustbot rustbot added the T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. label Jul 8, 2021
@jhpratt
Copy link
Member Author

jhpratt commented Aug 9, 2021

Closing in favor of #87517, which is the one linked to in code.

@jhpratt jhpratt closed this as completed Aug 9, 2021
matthiasgoergens added a commit to matthiasgoergens/fuse-backend-rs that referenced this issue Apr 5, 2023
The ci of docker-smoke gets errors otherwise:

````
error[E0658]: deriving `Default` on enums is experimental
   --> src/passthrough/mod.rs:345:17
    |
345 | #[derive(Debug, Default, Clone, Eq, PartialEq)]
    |                 ^^^^^^^
    |
    = note: see issue #86985 <rust-lang/rust#86985> for more information
    = note: this error originates in the derive macro `Default` (in Nightly builds, run with -Z macro-backtrace for more info)

For more information about this error, try `rustc --explain E0658`.
error: could not compile `fuse-backend-rs` due to previous error
make: *** [Makefile:4: build] Error 101
make: *** [Makefile:44: docker-smoke] Error 2
```
jiangliu pushed a commit to cloud-hypervisor/fuse-backend-rs that referenced this issue Apr 9, 2023
The ci of docker-smoke gets errors otherwise:

````
error[E0658]: deriving `Default` on enums is experimental
   --> src/passthrough/mod.rs:345:17
    |
345 | #[derive(Debug, Default, Clone, Eq, PartialEq)]
    |                 ^^^^^^^
    |
    = note: see issue #86985 <rust-lang/rust#86985> for more information
    = note: this error originates in the derive macro `Default` (in Nightly builds, run with -Z macro-backtrace for more info)

For more information about this error, try `rustc --explain E0658`.
error: could not compile `fuse-backend-rs` due to previous error
make: *** [Makefile:4: build] Error 101
make: *** [Makefile:44: docker-smoke] Error 2
```
nyetwurk added a commit to Blockdaemon/solana-accountsdb-plugin-kafka that referenced this issue Aug 22, 2023
… v0.6.3

flate 1.0.27 - rust-lang/rust#86985
reqwest 0.11.19 requires h2 v0.3.21 which requires rust 1.63.0
petgraph 0.6.4 requires indexmap 2.0.0 which requires hashbrown 0.14.0 and hence rust 1.64.0
don added a commit to don/posify that referenced this issue Aug 23, 2023
posify(snbc-880np) % cargo run --example match_manufacturer
   Compiling flate2 v1.0.27
   Compiling exr v1.7.0
error[E0658]: deriving `Default` on enums is experimental
  --> /Users/don/.cargo/registry/src/github.com-1ecc6299db9ec823/flate2-1.0.27/src/gz/mod.rs:90:17
   |
90 | #[derive(Debug, Default)]
   |                 ^^^^^^^
   |
   = note: see issue #86985 <rust-lang/rust#86985> for more information
   = note: this error originates in the derive macro `Default` (in Nightly builds, run with -Z macro-backtrace for more info)
fishilico added a commit to fishilico/shared that referenced this issue Jun 13, 2024
On Alpine 3.16 (Rust 1.60.0) and Fedora 34 (Rust 1.61.0):

    error[E0658]: deriving `Default` on enums is experimental
       --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/unicode-width-0.1.13/src/lib.rs:204:30
        |
    204 | #[derive(Clone, Copy, Debug, Default, PartialEq, Eq)]
        |                              ^^^^^^^
        |
        = note: see issue #86985 <rust-lang/rust#86985>
    for more information
        = note: this error originates in the derive macro `Default` (in
    Nightly builds, run with -Z macro-backtrace for more info)

    For more information about this error, try `rustc --explain E0658`.
blair61t added a commit to blair61t/rust-backend that referenced this issue Dec 2, 2024
The ci of docker-smoke gets errors otherwise:

````
error[E0658]: deriving `Default` on enums is experimental
   --> src/passthrough/mod.rs:345:17
    |
345 | #[derive(Debug, Default, Clone, Eq, PartialEq)]
    |                 ^^^^^^^
    |
    = note: see issue #86985 <rust-lang/rust#86985> for more information
    = note: this error originates in the derive macro `Default` (in Nightly builds, run with -Z macro-backtrace for more info)

For more information about this error, try `rustc --explain E0658`.
error: could not compile `fuse-backend-rs` due to previous error
make: *** [Makefile:4: build] Error 101
make: *** [Makefile:44: docker-smoke] Error 2
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC 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

2 participants