How to implement Iterator yielding mutable references

后端 未结 2 1181
南笙
南笙 2021-01-14 07:53

I am trying to implement a simple lookup iterator:

pub struct LookupIterMut<\'a, D> {
    data : &\'a mut          


        
2条回答
  •  无人共我
    2021-01-14 08:37

    Using unsafe

    Reminder: it is unsound to have, at any time, two accessible mutable references to the same underlying value.

    The crux of the problem is that the language cannot guarantee that the code abides by the above rule, should indices contain any duplicate, then the iterator as implemented would allow obtaining concurrently two mutable references to the same item in the slice, which is unsound.

    When the language cannot make the guarantee on its own, then you either need to find an alternative approach or you need to do your due diligence and then use unsafe.

    In this case, on the Playground:

    impl<'a, D> LookupIterMut<'a, D> {
        pub fn new(data: &'a mut [D], indices: &'a [usize]) -> Self {
            let set: HashSet = indices.iter().copied().collect();
            assert!(indices.len() == set.len(), "Duplicate indices!");
    
            Self { data, indices, i: 0 }
        }
    }
    
    impl<'a, D> Iterator for LookupIterMut<'a, D> {
        type Item = &'a mut D;
    
        fn next(&mut self) -> Option {
            if self.i >= self.indices.len() {
                None
            } else {
                let index = self.indices[self.i];
                assert!(index < self.data.len());
    
                self.i += 1;
    
                //  Safety:
                //  -   index is guaranteed to be within bounds.
                //  -   indices is guaranteed not to contain duplicates.
                Some(unsafe { &mut *self.data.as_mut_ptr().offset(index as isize) })
            }
        }
    }
    

    Performance wise, the construction of a HashSet in the constructor is rather unsatisfying but cannot really be avoided in general. If indices was guaranteed to be sorted for example, then the check could be performed without allocation.

提交回复
热议问题