You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
pnkfelix commentedon Feb 11, 2015
nominating, seems 1.0 beta to me.
pnkfelix commentedon Feb 11, 2015
(subtask of #5016, but gets higher priority due to (more) semantic visibility)
Feature-gate the `#[unsafe_no_drop_flag]` attribute.
SSheldon commentedon Feb 21, 2015
This feature gate doesn't seem to be required as of alpha 2. The following compiles without issue:
pnkfelix commentedon Feb 25, 2015
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.)
Turn `unsafe_no_drop_flag` back into a gated-feature.
Rollup merge of rust-lang#22787 - pnkfelix:reenable-gate-for-unsafe_n…