From: 046-301-5902@kylheku.com   
      
   On 2026-01-06, Kaz Kylheku <046-301-5902@kylheku.com> wrote:   
   > implications in the absence of restrict. Various ways of implemeting a   
   > memcpy-like function will produce various unexpected results when   
   > objects overlap, even without any undefined  behavior taking place. For   
   > instance if we copy byte-by-byte, from lowest address to highest, then   
   > we end up writing into memory that our loop is about to read from,   
   > corrupting the data.   
      
   I mean, of course, when we copy from a lower addressed object to a higher   
   addresed object which overlaps it.   
      
   --   
   TXR Programming Language: http://nongnu.org/txr   
   Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal   
   Mastodon: @Kazinator@mstdn.ca   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)