New lints: item that was previously public API is now #[doc(hidden)]
i.e. no longer public API
#578
Labels
A-lint
Area: new or existing lint
E-help-wanted
Call for participation: Help is requested to fix this issue.
E-mentor
Call for participation: Mentorship is available for this issue.
For example, uncommenting the
#[doc(hidden)]
line is a breaking change since the struct is no longer considered public API, even though it is public. This is because some non-public API may need to be accessible from outside its crate, for example in macro-heavy crates likepyo3
.We need lints for this kind of situation for:
union_now_doc_hidden
#679pub_module_level_const_now_doc_hidden
. #703ImplOwner
(struct/enum/union) inherent associated functions / methods: Inherent method now doc hidden #821ImplOwner
associated constants: Added inherent_associated_const_now_doc_hidden #820Remaining work item
We should figure out what are the appropriate semantics of marking an
impl
block#[doc(hidden)]
with respect to the block's contents. Are the contents considered not public API anymore? Is#[doc(hidden)]
simply ignored on thatimpl
block?The action items here are:
rustdoc
itself treats items defined inside a#[doc(hidden)]
impl block. Does it think they are hidden, or no?The text was updated successfully, but these errors were encountered: