Crate ouroboros_examples
source ·Modules
- Encapsulates implementation details for a self-referencing struct. This module is only visible when using –document-private-items.
- Encapsulates implementation details for a self-referencing struct. This module is only visible when using –document-private-items.
- Encapsulates implementation details for a self-referencing struct. This module is only visible when using –document-private-items.
- Encapsulates implementation details for a self-referencing struct. This module is only visible when using –document-private-items.
- Encapsulates implementation details for a self-referencing struct. This module is only visible when using –document-private-items.
- Encapsulates implementation details for a self-referencing struct. This module is only visible when using –document-private-items.
Structs
- The self-referencing struct.
- The self-referencing struct.
- The self-referencing struct.
- The self-referencing struct.
- The self-referencing struct.
- A more verbose but stable way to construct self-referencing structs. It is comparable to using
StructName { field1: value1, field2: value2 }
rather thanStructName::new(value1, value2)
. This has the dual benefit of making your code both easier to refactor and more readable. Callbuild()
to construct the actual struct. The fields of this struct should be used as follows: - A more verbose but stable way to construct self-referencing structs. It is comparable to using
StructName { field1: value1, field2: value2 }
rather thanStructName::new(value1, value2)
. This has the dual benefit of making your code both easier to refactor and more readable. Callbuild()
to construct the actual struct. The fields of this struct should be used as follows: - A more verbose but stable way to construct self-referencing structs. It is comparable to using
StructName { field1: value1, field2: value2 }
rather thanStructName::new(value1, value2)
. This has the dual benefit of making your code both easier to refactor and more readable. Calltry_build()
ortry_build_or_recover()
to construct the actual struct. The fields of this struct should be used as follows: - A more verbose but stable way to construct self-referencing structs. It is comparable to using
StructName { field1: value1, field2: value2 }
rather thanStructName::new(value1, value2)
. This has the dual benefit of making your code both easier to refactor and more readable. Calltry_build()
ortry_build_or_recover()
to construct the actual struct. The fields of this struct should be used as follows: - A more verbose but stable way to construct self-referencing structs. It is comparable to using
StructName { field1: value1, field2: value2 }
rather thanStructName::new(value1, value2)
. This has the dual benefit of making your code both easier to refactor and more readable. Callbuild()
to construct the actual struct. The fields of this struct should be used as follows: - A more verbose but stable way to construct self-referencing structs. It is comparable to using
StructName { field1: value1, field2: value2 }
rather thanStructName::new(value1, value2)
. This has the dual benefit of making your code both easier to refactor and more readable. Calltry_build()
ortry_build_or_recover()
to construct the actual struct. The fields of this struct should be used as follows: - The self-referencing struct.
- A more verbose but stable way to construct self-referencing structs. It is comparable to using
StructName { field1: value1, field2: value2 }
rather thanStructName::new(value1, value2)
. This has the dual benefit of making your code both easier to refactor and more readable. Callbuild()
to construct the actual struct. The fields of this struct should be used as follows: - A more verbose but stable way to construct self-referencing structs. It is comparable to using
StructName { field1: value1, field2: value2 }
rather thanStructName::new(value1, value2)
. This has the dual benefit of making your code both easier to refactor and more readable. Callbuild()
to construct the actual struct. The fields of this struct should be used as follows: - A more verbose but stable way to construct self-referencing structs. It is comparable to using
StructName { field1: value1, field2: value2 }
rather thanStructName::new(value1, value2)
. This has the dual benefit of making your code both easier to refactor and more readable. Calltry_build()
ortry_build_or_recover()
to construct the actual struct. The fields of this struct should be used as follows: - A more verbose but stable way to construct self-referencing structs. It is comparable to using
StructName { field1: value1, field2: value2 }
rather thanStructName::new(value1, value2)
. This has the dual benefit of making your code both easier to refactor and more readable. Calltry_build()
ortry_build_or_recover()
to construct the actual struct. The fields of this struct should be used as follows: - A more verbose but stable way to construct self-referencing structs. It is comparable to using
StructName { field1: value1, field2: value2 }
rather thanStructName::new(value1, value2)
. This has the dual benefit of making your code both easier to refactor and more readable. Callbuild()
to construct the actual struct. The fields of this struct should be used as follows: - A more verbose but stable way to construct self-referencing structs. It is comparable to using
StructName { field1: value1, field2: value2 }
rather thanStructName::new(value1, value2)
. This has the dual benefit of making your code both easier to refactor and more readable. Calltry_build()
ortry_build_or_recover()
to construct the actual struct. The fields of this struct should be used as follows: