RFC: Uninitialized Pointers #268

Activity

1. rust-highfive

   added

   postponedRFCs that have been postponed and may be revisited at a later time.RFCs that have been postponed and may be revisited at a later time.

   on Sep 24, 2014
2. nrc

   added

   T-langRelevant to the language team, which will review and decide on the RFC.Relevant to the language team, which will review and decide on the RFC.

   on Aug 17, 2016
3. withoutboats

   added a commit that references this issue on Jan 15, 2017

   Merge pull request rust-lang#268 from spinda/future-poll

   ...

   6b947d2
4. Centril

   added

   A-typesystemType system related proposals & ideasType system related proposals & ideas

   A-referencesProposals related to referencesProposals related to references

   A-uninit&uninit related proposals & ideas&uninit related proposals & ideas

   A-syntaxSyntax related proposals & ideasSyntax related proposals & ideas

   A-machineProposals relating to Rust's abstract machine.Proposals relating to Rust's abstract machine.

   on Nov 26, 2018
5. wycats

   added a commit that references this issue on Mar 5, 2019

   Merge pull request rust-lang#268 from emberjs/acceptance-testing

   ...

   1b3e82a
6. Lonami commented on Aug 22, 2019

   

   Lonami

   on Aug 22, 2019

   More actions

   What is the state of this after the shift to MaybeUninit?
7. RustyYato commented on Aug 22, 2019

   

   RustyYato

   on Aug 22, 2019

   More actions

   Given that my previous RFC #2534 was closed, with the reasoning being that we don't want to add too many more reference types and that MaybeUninit could serve all the use-cases of &uninit T well enough, I think that we aren't going to get uninitialized pointers/reference types.