I was not even aware about this terminology before. Stack and Heap seems to be a really common thing for low level languages, but since I'm new to Rust this article helped me a lot.
Rust borrow checker does not help with managing object hierarchies in heap. It works only around stack and helps only with synchronous function calls. It doesn't work with asynchronous and multithreaded code. Also Rust does not prevent memory leaks.
Technically, &str is simply a reference (an address) which is a fixed size that may point to dynamically created data or static. The only thing on the stack is the address itself, not the actual data, because the slice can also refer to gigabytes of data. I just wanted to make sure there was no confusion and people assumed the slice was a value type. Nice article, btw!
My name is William Rodrigues, but everyone calls me Will. I study a little about everything, but what I like the most is back-end development. My main technologies are Python, Node.js and Java.
While Rust's memory management may pose initial challenges for beginners, it proves remarkably powerful once mastered. And this article helped me to make this.
Great article Canhassi it was really insightful. I noticed a couple of grammatical errors though, you can checkout grammarly to help you refine your articles.👍
Hi! I'm currently working as Site Reliability Engineer, here I will share my knowledge and experiences at work and life :) Most of my content will be in PT/BR and for beginners!
I have never used Rust and don't really intend to, but this article was still fascinating, especially since I suspect those concept are relevant in many other languages.
Hi, my name is Gustavo de Camargo Campos. I'm 22y old. My stacks are Laravel as backend and Vue.js as frontend. I'm an enthusiastic student of Laravel.
I was not even aware about this terminology before. Stack and Heap seems to be a really common thing for low level languages, but since I'm new to Rust this article helped me a lot.
Thanks for the contribution!
OMG Canhas? Big fan here! Great content man!
Rust borrow checker does not help with managing object hierarchies in heap. It works only around stack and helps only with synchronous function calls. It doesn't work with asynchronous and multithreaded code. Also Rust does not prevent memory leaks.
Awesome!!
Good articles.
In multi thread, pay attention to race conditions with references like
print_name(&name);
Technically, &str is simply a reference (an address) which is a fixed size that may point to dynamically created data or static. The only thing on the stack is the address itself, not the actual data, because the slice can also refer to gigabytes of data. I just wanted to make sure there was no confusion and people assumed the slice was a value type. Nice article, btw!
Thank you for the explanation <3
While Rust's memory management may pose initial challenges for beginners, it proves remarkably powerful once mastered. And this article helped me to make this.
Great article
Great article <3
Awesome!!
Great Article, Cousin
Great article, congratulations on the content!
Awesome!
Great article Canhassi it was really insightful. I noticed a couple of grammatical errors though, you can checkout grammarly to help you refine your articles.👍
thank you for the feedback!!
Great article for Rustacean. Thanks a lot🙏
top demais mano
Nicee Canhas
Such an inspiration
great article cousin!
amazing content, thanks for writing it
Great article cousin, this was such a headache to understand when I was learning rust , your didactics made it quite clear!
Thanks a lot
I have never used Rust and don't really intend to, but this article was still fascinating, especially since I suspect those concept are relevant in many other languages.
Thanks !
I'm really surprise with the feature, I had no idea about is. Congrats
djobzy.com/blog-details/engineerin...