c_void has wrong rustc support level in docs #55619

Activity

1. Proximyst commented on Nov 3, 2018

   

   Proximyst

   on Nov 3, 2018

   More actions

   While the module c_void lays in, core::ffi, was stabilised at 1.30.0, the type c_void was stabilised at 1.1.0, which again makes the docs correct. The docs for the module core::ffi say 1.30.0.
2. jethrogb commented on Nov 3, 2018

   

   jethrogb

   on Nov 3, 2018

   ContributorAuthor

   More actions

   which again makes the docs correct.

   I guess that's a matter of perspective. I think minimum versions of parent items should trickle down to child items such that you don't have to walk up the module tree in the documentation to find out whether something is available or not.
3. IsaacWoods commented on Nov 4, 2018

   

   IsaacWoods

   on Nov 4, 2018

   Contributor

   More actions

   So I did the original PR to create core::ffi::c_void, and probably agree with @jethrogb in hindsight. The c_void type was originally available at std::os::raw::c_void, which should stay at 1.1.0. However, both std::ffi::c_void and core::ffi::c_void should probably be changed to 1.30.0.
4. ExpHP commented on Nov 6, 2018

   

   ExpHP

   on Nov 6, 2018

   Last edited by ExpHP

   Contributor

   More actions

   This has happened before as well: #49651
5. jonas-schievink

   added

   A-stabilityArea: `#[stable]`, `#[unstable]` etc.Area: `#[stable]`, `#[unstable]` etc.

   on Jan 27, 2019
6. tmandry

   added a commit that references this issue on Oct 29, 2019

   Rollup merge of rust-lang#65930 - lzutao:new-feature-gate-c_void, r=d…

   ...

   This issue will close once commit 73dcb96 is merged into the 'main' branch.

   73dcb96
7. bors

   closed this as completedin 73dcb96on Oct 29, 2019