update attribute not working on internal struct?

[yanshay]

update attribute not working on internal struct?

[wcampbell0x2a]

Recursive update seems like a good thing to add. Anyway, here is the "requires Clone + Copy and is really just a hack" code you can use:

#[derive(Debug, PartialEq, DekuRead, DekuWrite, Clone, Copy)]
struct IpAddr {
    #[deku(update = "9")]
    a: u8,
    b: u8,
    c: u8,
    d: u8,
}

#[derive(Debug, PartialEq, DekuRead, DekuWrite)]
struct Container {
    #[deku(update = "{ let mut a = self.ip_addr; a.update()?; a }")]
    ip_addr: IpAddr,
}

[yanshay]

This works for this case, however I also have a Vec in the relevant structure, and for this to work it is required for IpAddr implement Clone and Copy, but Vec doesn't implement Copy, so it can't work. Is there a way to bypass it?

What I did was to simply implement my own update function on Container that calls the IpAddr update. Not sure why the update through Deku requires IpAddr to implement Copy when my own function doesn't (maybe because it accepts &mut self)

[wcampbell0x2a]

deku emits the following for updating, for my example:

impl DekuUpdate for Container {
    fn update(&mut self) -> core::result::Result<(), ::deku::DekuError> {
        use core::convert::TryInto;
        self
            .ip_addr = ({
            let mut a = self.ip_addr;
            a.update()?;
            a
        })
            .try_into()?;
        Ok(())
    }
}

There isn't a reason that deku couldn't in the future support emitting this:

impl DekuUpdate for Container {
    fn update(&mut self) -> core::result::Result<(), ::deku::DekuError> {
        self.ip_addr.update()?;
        Ok(())
    }
}

Maybe allow an empty update for this behavior? I'll admit I don't use the update attribute much.

#[derive(Debug, PartialEq, DekuRead, DekuWrite)]
struct Container {
    #[deku(update)]
    ip_addr: IpAddr,
}