我从Rust开始,我已经面临着数据所有权的问题。
我想实现一个名为Port<T>的泛型结构,它有一个值为Vec<T>的向量。此外,此结构还具有引用计数指针的向量,这些指针指向相同类型的其他结构Vec<Rc<Port<T>>>
use std::slice::Iter;
use std::rc::Rc;
pub struct Port<T> {
values: Vec<T>,
ports: Vec<Rc<Port<T>>>,
}其思想如下:有多个Port<T>类型的结构。您可以将T类型的值添加到给定端口。每个端口将这些值存储在其values属性中。但是,可以使用引用计数指针将一个端口“链接”到其他端口:
impl <T> Port<T> {
pub fn new() -> Self {
Self { values: vec![], ports: vec![] }
}
pub fn add_value(&mut self, value: T) {
self.values.push(value);
}
pub fn chain_port(&mut self, port: Rc<Port<T>>) {
if !port.is_empty() {
self.ports.push(port)
}
}
pub fn is_empty(&self) -> bool {
self.values.is_empty() || self.ports.is_empty()
}
pub fn clear(&mut self) {
self.values.clear();
self.ports.clear();
}
}到目前为止,代码已经编译完毕。现在,我想为一个端口实现一个迭代器,它返回对此端口拥有的值的引用,也返回对每个链接端口的迭代器生成的值的引用:
pub struct PortIterator<'a, T> {
values: Iter<'a, T>, // Iterates over values owned by Port<T>
port: Option<Box<PortIterator<'a, T>>>, // Pointer to current port iterator
ports: Vec<Rc<Port<T>>>, // Pointers to remaining chained ports
}
// Note that the iterator is created from an immutable reference to Port<T>
impl<'a, T: 'a> IntoIterator for &'a Port<T> {
type Item = &'a T; // the iterator returns references to values
type IntoIter = PortIterator<'a, T>;
fn into_iter(self) -> Self::IntoIter {
// We clone all the reference-counting pointers so the iterator owns them
let mut ports = vec![];
for port in self.ports.iter() {
ports.push(port.clone())
}
PortIterator {values: self.values.iter(), port: None, ports}
}
}现在,让我们为PortIterator定义Iterator特征
impl <'a, T: 'a> Iterator for PortIterator<'a, T> {
type Item = &'a T;
fn next(&mut self) -> Option<Self::Item> {
// We first iterate over values of the original port
if let Some(v) = self.values.next() {
return Some(v)
}
// If the first iterable is done, we try to iterate over a chained port
if let Some(port) = &mut self.port {
if let Some(v) = port.next() {
return Some(v)
}
}
// if the chained port is over, we try to consume the next chained port
if let Some(port) = self.ports.get(self.next_port) {
self.next_port += 1;
self.port = Some(Box::new(port.as_ref().into_iter()));
return self.next()
}
None
}
}现在,程序不能编译。问题似乎出现在第三个if let块中,而且它与生命周期有关。这是编译器所说的:
error[E0495]: cannot infer an appropriate lifetime for lifetime parameter in function call due to conflicting requirements
--> src/modeling/port.rs:69:40
|
69 | if let Some(port) = self.ports.get(self.next_port) {
| ^^^
|
note: first, the lifetime cannot outlive the anonymous lifetime #1 defined on the method body at 57:5...
--> src/modeling/port.rs:57:5
|
57 | fn next(&mut self) -> Option<Self::Item> {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...so that reference does not outlive borrowed content
--> src/modeling/port.rs:69:29
|
69 | if let Some(port) = self.ports.get(self.next_port) {
| ^^^^^^^^^^
note: but, the lifetime must be valid for the lifetime `'a` as defined on the impl at 54:7...
--> src/modeling/port.rs:54:7
|
54 | impl <'a, T: 'a> Iterator for PortIterator<'a, T> {
| ^^
note: ...so that the expression is assignable
--> src/modeling/port.rs:71:25
|
71 | self.port = Some(Box::new(port.as_ref().into_iter()));
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
= note: expected `Option<Box<PortIterator<'a, _>>>`
found `Option<Box<PortIterator<'_, _>>>`我不知道该怎么处理这件事。我一直在尝试其他选择和实现,但我一直在原地踏步。
发布于 2021-06-07 21:10:27
我认为有更简单的方法可以实现你想要的目标。让我们从小开始:Port<T>需要一个iter(&self)方法,该方法返回分发&T项的迭代器:
pub fn iter(&self) -> impl Iterator<Item = &T> {
// ...
}此函数需要在self.values上链接迭代器,即在链接的端口上使用迭代器的self.values.iter()。你想写的东西是这样的:
pub fn iter(&self) -> impl Iterator<Item = &T> {
self.values
.iter()
.chain(self.ports.iter().flat_map(|p| p.iter()))
}但是,这不能编译,因为编译器抱怨“递归不透明类型”。这是因为p.iter()的类型与我们的impl Iterator<...>完全相同,因此它必须包含它自己。从概念上讲,这与您在构建PortIterator时遇到的问题相同,您通过装箱链接的PortIterator解决了这个问题。我们可以用同样的方式来解决它,通过装箱内部迭代器并动态分派它:
pub fn iter(&self) -> impl Iterator<Item = &T> {
self.values.iter().chain(
self.ports
.iter()
.flat_map(|p| Box::new(p.iter()) as Box<dyn Iterator<Item = &T>>),
)
}https://stackoverflow.com/questions/67870844
复制相似问题