I'd like to create an Rc<str>
because I want reduce the indirection from following the 2 pointers that accessing an Rc<String>
requires. I need to use an Rc
because I truly have shared ownership. I detail in another question more specific issues I have around my string type.
Rc has a ?Sized
bound:
pub struct Rc<T: ?Sized> { /* fields omitted */ }
I've also heard that Rust 1.2 will come with proper support for storing unsized types in an Rc
, but I'm unsure how this differs from 1.1.
Taking the str
case as example, my naive attempt (also this for building from a String
) fails with:
use std::rc::Rc;
fn main() {
let a: &str = "test";
let b: Rc<str> = Rc::new(*a);
println!("{}", b);
}
error[E0277]: the trait bound `str: std::marker::Sized` is not satisfied
--> src/main.rs:5:22
|
5 | let b: Rc<str> = Rc::new(*a);
| ^^^^^^^ `str` does not have a constant size known at compile-time
|
= help: the trait `std::marker::Sized` is not implemented for `str`
= note: required by `<std::rc::Rc<T>>::new`
It's clear that in order to create an Rc<str>
, I need to copy the whole string: RcBox
would be itself an unsized type, storing the string itself alongside the weak and strong pointers — the naive code above doesn't even make sense.
I've been told that one can not instantiate such type, but instead instantiate an Rc<T>
with a sized T
and then coerce it to an unsized type. The example given is for the storing a trait object: first create Rc<ConcreteType>
and then coerce to Rc<Trait>
. But this doesn't make sense either: neither this nor this work (and you can't coerce from &str
or String
to str
anyway).
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…