It looks like the conflict is that the return value:
- Must be valid for at least the lifetime
'a
- Must not outlive
&mut self
, which is only the lifetime of the function call.
If this were allowed, it would let you call it twice and get two &'a mut
references to the same String
contents:
let mut w = RefWrap { wrap: &mut s };
let ref1 = w.unwrap();
let ref2 = w.unwrap(); // two mutable references!
The reason is that the way Rust reasons about whether something is borrowed is by tying lifetimes together - but here you are explicitly saying that the return value's lifetime is unrelated to &mut self
, which means it doesn't extend the borrow - and then you can borrow again with another call.
The solution here, to get the original reference lifetime out without risking a second &mut
reference overlapping it, is to take self
by value (move) so that it can't be used again. The compiler is happy with this:
impl<'a> RefWrap<'a> {
fn unwrap(self) -> &'a mut String {
match *self.wrap {
Some(ref mut s) => s,
None => panic!(),
}
}
}
(Playground)
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…