Skip to content

/rust

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

Nonparametric dropck (tracking issue for RFC 1238) #28498

Open
nikomatsakis opened this Issue Sep 18, 2015 · 6 comments

Comments

Assignees

@pnkfelix pnkfelix

Labels
B-RFC-implemented B-unstable C-tracking-issue P-medium T-lang
Projects
None yet
Milestone
No milestone
8 participants
@nikomatsakis @alexcrichton @SimonSapin @steveklabnik @pnkfelix @nrc @Mark-Simulacrum @rust-highfive
@nikomatsakis
Copy link
Contributor

nikomatsakis commented Sep 18, 2015 •
edited by pnkfelix

Tracking issue for rust-lang/rfcs#1238.

  • subtask: #[may_dangle] attribute #34761
  • can't close this until support for we have stable support for 3rd party collection types

cc @pnkfelix

@nikomatsakis nikomatsakis added the B-RFC-approved label Sep 18, 2015

@nikomatsakis

This comment has been minimized.

Sign in to view
Copy link
Contributor Author

nikomatsakis commented Sep 18, 2015

triage: P-high

@rust-highfive rust-highfive added the P-high label Sep 18, 2015

@nikomatsakis nikomatsakis assigned pnkfelix Sep 18, 2015

@pnkfelix pnkfelix referenced this issue Oct 6, 2015

Merged

implement RFC 1238: nonparametric dropck. #28861

bors added a commit that referenced this issue Oct 10, 2015

@bors
Auto merge of #28861 - pnkfelix:fsk-nonparam-dropck-issue28498, r=ari… 
…elb1

implement RFC 1238: nonparametric dropck.

cc #28498 

cc @nikomatsakis
Loading status checks…
87cd2c0
@nikomatsakis

This comment has been minimized.

Sign in to view
Copy link
Contributor Author

nikomatsakis commented Oct 29, 2015

triage: P-medium

@rust-highfive rust-highfive added P-medium and removed P-high labels Oct 29, 2015

@alexcrichton

This comment has been minimized.

Sign in to view
Copy link
Member

alexcrichton commented Feb 18, 2016

I think this was since implemented, so closing (but please reopen if there's something left!)

@alexcrichton alexcrichton closed this Feb 18, 2016

@SimonSapin

This comment has been minimized.

Sign in to view
Copy link
Contributor

SimonSapin commented May 4, 2016 •
edited

I think this should be reopened with the B-unstable label. The RFC is implemented, but the #[unsafe_destructor_blind_to_params] attribute is still behind the dropck_parametricity feature gate which points to this as its tracking issue.

#[unsafe_destructor_blind_to_params] is used for Vec and a number of other types defined in the standard library. It isn’t any less useful for types outside the standard library. I’ve needed it for an arena allocator.

@nikomatsakis nikomatsakis added the B-unstable label May 4, 2016

@nikomatsakis

This comment has been minimized.

Sign in to view
Copy link
Contributor Author

nikomatsakis commented May 4, 2016

I agree.

@nikomatsakis nikomatsakis reopened this May 4, 2016

@nrc nrc added the T-lang label Aug 19, 2016

@nrc nrc added B-RFC-implemented and removed B-RFC-approved labels Aug 29, 2016

@pnkfelix pnkfelix referenced this issue Oct 10, 2016

Open

`#[may_dangle]`, a refined dropck escape hatch (tracking issue for RFC 1327) #34761

5 of 7 tasks complete

@Mark-Simulacrum Mark-Simulacrum added the C-tracking-issue label Jul 22, 2017

@steveklabnik

This comment has been minimized.

Sign in to view
Copy link
Member

steveklabnik commented Mar 12, 2019

Triage: feature gate still active, not aware of any work in this area.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.