@@ -10,7 +10,7 @@ This allows moving and dropping of a `OwningRef` without needing to recreate the
1010This can sometimes be useful because Rust borrowing rules normally prevent
1111moving a type that has been moved from. For example, this kind of code gets rejected:
1212
13- ```rust,ignore
13+ ```compile_fail,E0515
1414fn return_owned_and_referenced<'a>() -> (Vec<u8>, &'a [u8]) {
1515 let v = vec![1, 2, 3, 4];
1616 let s = &v[1..3];
@@ -43,7 +43,8 @@ and preventing mutable access to root containers, which in practice requires hea
4343as provided by `Box<T>`, `Rc<T>`, etc.
4444
4545Also provided are typedefs for common owner type combinations,
46- which allow for less verbose type signatures. For example, `BoxRef<T>` instead of `OwningRef<Box<T>, T>`.
46+ which allow for less verbose type signatures.
47+ For example, `BoxRef<T>` instead of `OwningRef<Box<T>, T>`.
4748
4849The crate also provides the more advanced `OwningHandle` type,
4950which allows more freedom in bundling a dependent handle object
@@ -495,7 +496,8 @@ impl<O, T: ?Sized> OwningRef<O, T> {
495496 }
496497 }
497498
498- /// Erases the concrete base type of the owner with a trait object which implements `Send` and `Sync`.
499+ /// Erases the concrete base type of the owner with a trait object
500+ /// which implements `Send` and `Sync`.
499501 ///
500502 /// This allows mixing of owned references with different owner base types.
501503 pub fn erase_send_sync_owner < ' a > ( self ) -> OwningRef < O :: Erased , T >
@@ -507,7 +509,7 @@ impl<O, T: ?Sized> OwningRef<O, T> {
507509 }
508510 }
509511
510- // TODO : wrap_owner
512+ // UNIMPLEMENTED : wrap_owner
511513
512514 // FIXME: Naming convention?
513515 /// A getter for the underlying owner.
@@ -753,7 +755,7 @@ impl<O, T: ?Sized> OwningRefMut<O, T> {
753755 }
754756 }
755757
756- // TODO : wrap_owner
758+ // UNIMPLEMENTED : wrap_owner
757759
758760 // FIXME: Naming convention?
759761 /// A getter for the underlying owner.
0 commit comments