• 2xsaiko@discuss.tchncs.de
    link
    fedilink
    arrow-up
    7
    ·
    5 months ago

    I’m curious how they plan on implementing interior references while keeping structs that contain them movable and without breaking the “moving structs is always just memcpy” assumption.

    All of these would be great to have though, would make the language a lot more ergonomic. I hope they get implemented.

    • Giooschi@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 months ago

      It’s mentioned in footnote 6:

      As an example, to make this work I’m assuming some kind of “true deref” trait that indicates that Deref yields a reference that remains valid even as the value being deref’d moves from place to place. We need a trait much like this for other reasons too.

      It would only work for references that are stable after the value they reference is moved. Think for example of a &str you get from a String.