Re-exportsยง
pub use pulldown_cmark;
Structsยง
- DocFragment
- A portion of documentation, extracted from a
#[doc]attribute.
Enumsยง
Functionsยง
- add_
doc_ fragment - The goal of this function is to apply the
DocFragmenttransformation that is required when transforming into the final Markdown, which is applying the computed indent to each line in each doc fragment (aDocFragmentcan contain multiple lines in case of#[doc = ""]). - attrs_
to_ doc_ fragments - attrs_
to_ ๐preprocessed_ links - Simplified version of
preprocessed_markdown_linksfrom rustdoc. Must return at least the same links as it, but may add some more links on top of that. - collect_
link_ ๐data - Collects additional data of link.
- has_
primitive_ or_ keyword_ or_ attribute_ docs - Has
#[rustc_doc_primitive]or#[doc(keyword)]or#[doc(attribute)]. - inner_
docs - Returns whether the first doc-comment is an inner attribute.
- main_
body_ opts - Options for rendering Markdown in the main body of documentation.
- may_
be_ doc_ link - Keep inline and reference links
[], but skip autolinks<>which we never consider to be intra-doc links. - parse_
links ๐ - Similar version of
markdown_linksfrom rustdoc. This will collect destination links and display text if exists. - prepare_
to_ doc_ link_ resolution - Return the doc-comments on this item, grouped by the module they came from. The module can be different if this is a re-export with added documentation.
- preprocess_
link ๐ - Simplified version of the corresponding function in rustdoc.
- source_
span_ for_ markdown_ range - Attempts to match a range of bytes from parsed markdown to a
Spanin the source code. - source_
span_ for_ markdown_ range_ inner - span_
of_ fragments - Returns a span encompassing all the document fragments.
- strip_
generics_ from_ path - strip_
generics_ ๐from_ path_ segment - unindent_
doc_ fragments - Removes excess indentation on comments in order for the Markdown to be parsed correctly. This is necessary because the convention for writing documentation is to provide a space between the /// or //! marker and the doc text, but Markdown is whitespace-sensitive. For example, a block of text with four-space indentation is parsed as a code block, so if we didnโt unindent comments, these list items