Your videos are very helpful, thank you! You explain stuff very well. Thank you for investing time to these very professional and great videos. I'm attempting to convert a Java SpringBoot micro service to Rust, figuring out how to use a HashMap between threads. The concepts explained here are very helpful to understand what people discuss on Stack Overflow.
Great Video This part of rust is very difficult to get specifically if you come from is/python background. Very hard learning curve for rust only due to ownership/borrow concept on Rust. Else very awesome language which is fast.
Very confusing and it looks logically inconsistent. First it says there can be only one owner. But later it is Ok for r1 and r2 to own the same variable. A mess.
Your videos are very helpful, thank you! You explain stuff very well. Thank you for investing time to these very professional and great videos. I'm attempting to convert a Java SpringBoot micro service to Rust, figuring out how to use a HashMap between threads. The concepts explained here are very helpful to understand what people discuss on Stack Overflow.
Great Video
This part of rust is very difficult to get specifically if you come from is/python background.
Very hard learning curve for rust only due to ownership/borrow concept on Rust.
Else very awesome language which is fast.
These videos are very appreciated, Ricky 😁 Cheers from South Africa
🤟
I really appreciate your content, but I always here "welcome to the death method" 😕
Very confusing and it looks logically inconsistent. First it says there can be only one owner. But later it is Ok for r1 and r2 to own the same variable. A mess.
I'd encourage you to watch that section of the video again as it clearly explains your misunderstanding of the given concept.
r1 and r2 borrows value, doesn't owns them, ownership of value still remains with 's'.