Crate ouroboros_examples

Modules

• ouroboros_impl_chain 🔒
  Encapsulates implementation details for a self-referencing struct. This module is only visible when using –document-private-items.
• ouroboros_impl_data_and_ref 🔒
  Encapsulates implementation details for a self-referencing struct. This module is only visible when using –document-private-items.
• ouroboros_impl_documentation_example 🔒
  Encapsulates implementation details for a self-referencing struct. This module is only visible when using –document-private-items.
• ouroboros_impl_undocumented 🔒
  Encapsulates implementation details for a self-referencing struct. This module is only visible when using –document-private-items.
• ouroboros_impl_visibility 🔒
  Encapsulates implementation details for a self-referencing struct. This module is only visible when using –document-private-items.
• ouroboros_impl_with_const_param 🔒
  Encapsulates implementation details for a self-referencing struct. This module is only visible when using –document-private-items.

Structs

• Chain
  The self-referencing struct.
• DataAndRef
  The self-referencing struct.
• DocumentationExample
  The self-referencing struct.
• Ext
• Undocumented
  The self-referencing struct.
• Visibility
  The self-referencing struct.
• VisibilityAsyncBuilder
  A more verbose but stable way to construct self-referencing structs. It is comparable to using StructName { field1: value1, field2: value2 } rather than StructName::new(value1, value2). This has the dual benefit of making your code both easier to refactor and more readable. Call build() to construct the actual struct. The fields of this struct should be used as follows:
• VisibilityAsyncSendBuilder
  A more verbose but stable way to construct self-referencing structs. It is comparable to using StructName { field1: value1, field2: value2 } rather than StructName::new(value1, value2). This has the dual benefit of making your code both easier to refactor and more readable. Call build() to construct the actual struct. The fields of this struct should be used as follows:
• VisibilityAsyncSendTryBuilder
  A more verbose but stable way to construct self-referencing structs. It is comparable to using StructName { field1: value1, field2: value2 } rather than StructName::new(value1, value2). This has the dual benefit of making your code both easier to refactor and more readable. Call try_build() or try_build_or_recover() to construct the actual struct. The fields of this struct should be used as follows:
• VisibilityAsyncTryBuilder
  A more verbose but stable way to construct self-referencing structs. It is comparable to using StructName { field1: value1, field2: value2 } rather than StructName::new(value1, value2). This has the dual benefit of making your code both easier to refactor and more readable. Call try_build() or try_build_or_recover() to construct the actual struct. The fields of this struct should be used as follows:
• VisibilityBuilder
  A more verbose but stable way to construct self-referencing structs. It is comparable to using StructName { field1: value1, field2: value2 } rather than StructName::new(value1, value2). This has the dual benefit of making your code both easier to refactor and more readable. Call build() to construct the actual struct. The fields of this struct should be used as follows:
• VisibilityTryBuilder
  A more verbose but stable way to construct self-referencing structs. It is comparable to using StructName { field1: value1, field2: value2 } rather than StructName::new(value1, value2). This has the dual benefit of making your code both easier to refactor and more readable. Call try_build() or try_build_or_recover() to construct the actual struct. The fields of this struct should be used as follows:
• WithConstParam
  The self-referencing struct.
• WithConstParamAsyncBuilder
  A more verbose but stable way to construct self-referencing structs. It is comparable to using StructName { field1: value1, field2: value2 } rather than StructName::new(value1, value2). This has the dual benefit of making your code both easier to refactor and more readable. Call build() to construct the actual struct. The fields of this struct should be used as follows:
• WithConstParamAsyncSendBuilder
  A more verbose but stable way to construct self-referencing structs. It is comparable to using StructName { field1: value1, field2: value2 } rather than StructName::new(value1, value2). This has the dual benefit of making your code both easier to refactor and more readable. Call build() to construct the actual struct. The fields of this struct should be used as follows:
• WithConstParamAsyncSendTryBuilder
  A more verbose but stable way to construct self-referencing structs. It is comparable to using StructName { field1: value1, field2: value2 } rather than StructName::new(value1, value2). This has the dual benefit of making your code both easier to refactor and more readable. Call try_build() or try_build_or_recover() to construct the actual struct. The fields of this struct should be used as follows:
• WithConstParamAsyncTryBuilder
  A more verbose but stable way to construct self-referencing structs. It is comparable to using StructName { field1: value1, field2: value2 } rather than StructName::new(value1, value2). This has the dual benefit of making your code both easier to refactor and more readable. Call try_build() or try_build_or_recover() to construct the actual struct. The fields of this struct should be used as follows:
• WithConstParamBuilder
  A more verbose but stable way to construct self-referencing structs. It is comparable to using StructName { field1: value1, field2: value2 } rather than StructName::new(value1, value2). This has the dual benefit of making your code both easier to refactor and more readable. Call build() to construct the actual struct. The fields of this struct should be used as follows:
• WithConstParamTryBuilder
  A more verbose but stable way to construct self-referencing structs. It is comparable to using StructName { field1: value1, field2: value2 } rather than StructName::new(value1, value2). This has the dual benefit of making your code both easier to refactor and more readable. Call try_build() or try_build_or_recover() to construct the actual struct. The fields of this struct should be used as follows: