Thanks! For this I'd prefer to have one of (a) leave them private and users use the &-returning methods, or (b) make them public but document them and explain why they might be used. I don't mind either one, but I'd prefer to not be in the current state where they're public-but-hidden as that feels a bit too brittle to me (e.g. easy to forget why they were public in the first place)

I have a better fix now. The original get function elides the lifetime, so we have fn get(&'b self) -> &'b T. But since Borrow<'a> is valid for the whole 'a duration, we should be able to borrow &'a T instead. The new signature is also semantically more accurate.