From: alexfrunews@gmail.com   
      
   On Saturday, May 6, 2023 at 6:01:23 PM UTC-7, Dan Cross wrote:   
   > In article <92ae547c-e14a-48e1...@googlegroups.com>,   
   > Alexei A. Frounze  wrote:    
   ...   
   > >I'm seeing repeated stories on Linux and Windows supporting    
   > >rust or moving towards C/C++ to rust conversion. I'm interested    
   > >in rust too, but I got stuck somewhere in the borrower chapters    
   > >in the documentation. Do you think the official docs are the best    
   > >description of those lifetime annotations and such? Or is there    
   > >something better, with gentler introduction?   
   > I'm not sure about a gentler introduction. I first learned via    
   > the O'Reilly book, personally, and I liked it very much.    
   >    
   > It's a bit of a joke that all new Rust programmers go through    
   > a phase of, "fighting the borrow-checker." (Followed shortly by    
   > the "traits are AWESOME, let's use them EVERYWHERE!" phase).    
      
   :) I'm not fighting it (yet). I think I get the basic idea (or one of the   
   few) that the allocations/lifetimes are nested (entirely or largely,   
   unless we're using the unsafe escapes), but I got confused with   
   some details and put it aside. Should work out those details at   
   some point.   
      
   > Personally, I like just cracking it open and playing around with    
   > a language to learn it, but that's just me.    
      
   I was hoping, I'd just read the relevant chapters, but I might   
   end up doing just the same, writing code as aid. I expect my code   
   compiling and working being more of a proof of the soundness   
   of the code with rust than with C/C++. Though I think rust   
   still got some things wrong (e.g. different overflow handling in   
   debug vs release), but overall it seems a step in the right direction.   
   Perhaps, a few steps, not just one. :)   
      
   Alex   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)