snaggen
You are free to see this as an ad, but as Rust is targeting safety critical programming in general, I find it interesting to follow certification efforts like this to make rust available for really safety critical use cases. Now, the Ferrocene project is contributing back, but that fact or the license does not really affect the relevance for this community.
It might be interesting to watch the Jackie Chan episode of Every Frame is a Painting, for an analysis of the difference between Hollywood and Hong Kong. This will explain why Jackie Chan is so much better in his Hong Kong movies.
I guess this answeres my previous question about the lack of updates to the Intellij Rust plugin.
The borrow checker handles more than just freeing allocated memory, it will also prevent data races and invalid concurrent access aso. I personally don’t have any issues with using garbage collected languages, but the fearless concurrency is nothing I’m willing to give up.
Great to see that this moves forward in a steady pace. And being able to compile Rust for Linux seems like a nice milestone, especially since many objections initially against rust in the kernel was about GCC support.
A reference &T holds a pointer, ie. the memory adress to the actual content of T
So, in the example x doesn’t hold the value 42, it holds the memory adress to the memory there the integer value 42 is stored. So, to access the value, you need to dereference the reference. Which is why you need to use *x when you assign the value.
If I look at what I use and what annoys me, I would have like to see focus on ‘Dyn async trait’ and ‘Traits for being generic over runtimes’. I think it is quite annoying that you have to decide on a whole eco-system when you are doing async code. I have had times when I have search for a very niched library, only to find that it is written for the wrong async runtime. And the longer it takes to correct this, the more cemented it will be.
I think this is was a great read, since it shows a few important things
- Coming to rust from C is not trivial, you are required to learn a few new concepts (or not really new, but implicit in most languages, formalized in rust).
- When coming from C and you understand the basic concepts, it is easier to learn rust than from many other languages, since you understand what is going on under the hood. Dangling pointers, and use after free aso, are known concepts. C/C++ programmers don’t have to fear rust.
- The rust book is a great source of information.
I hope this means that it will be easier for Lemmy to support the passkey standard. Now, I assume it will take a while until this is production ready, since the standard seems to be in a quite early stage.
