Skip to content

feature-gate unsafe_no_drop_flag #22173

Description

@pnkfelix

As part of non-zeroing dynamic drop (RFC 320), we need to feature-gate unsafe_no_drop_flag so that users do not come to rely on its unstable semantics when we release 1.0.

Activity

  1. pnkfelix commented on Feb 11, 2015

    @pnkfelix
    ContributorAuthor

    nominating, seems 1.0 beta to me.

  2. self-assigned this
    on Feb 11, 2015
  3. pnkfelix commented on Feb 11, 2015

    @pnkfelix
    ContributorAuthor

    (subtask of #5016, but gets higher priority due to (more) semantic visibility)

  4. added a commit that references this issue on Feb 11, 2015
    f9a1087
  5. SSheldon commented on Feb 21, 2015

    @SSheldon
    Contributor

    This feature gate doesn't seem to be required as of alpha 2. The following compiles without issue:

    #[unsafe_no_drop_flag]
    struct Foo;
    
    impl Drop for Foo {
        fn drop(&mut self) {
            println!("Dropping");
        }
    }
    
    fn main() { }
  6. pnkfelix commented on Feb 25, 2015

    @pnkfelix
    ContributorAuthor

    it seems like PR #22364 may have accidentally have removed the gating of unsafe_no_drop_flag.

    (That's what I deserve for not including a regression test on this.)

    I think I know how to fix this. (And I will look into making sure all of the feature-gated things have tests.)

  7. added a commit that references this issue on Feb 25, 2015
    5d7e283
  8. added a commit that references this issue on Feb 25, 2015
    f164254
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions