Ja und Nein, denn Rust ist im grunde sicherer aber auch das kommt darauf an wie mensch es umsetzt. Ich vertraue Rust mehr als anderes Coding, ich schau mir die Libs-Daten an.
»Speichersicherheit – Fast 20 Prozent aller Rust-Pakete sind potenziell unsicher:
Nach Angaben der Rust Foundation verwendet etwa jedes fünfte Rust-Paket das Unsafe-Keyword. Meistens werden dadurch Code oder Bibliotheken von Drittanbietern aufgerufen.«
Expand glob imports is an underrated feature of Rust Analyzer. It’s amazing how the black box melts away when you understand what your framework is bringing into scope.
I think there would be still space for systems programming language with a constraint from day zero that it would 1:1 compatible with plain C”s binary layout and memory model:
Roughly just .text, .bss, .rodata and ,data.
No symbol mangling at all.
All the memory safety etc. fancy features would be then designed within exactly those constraints.
#Rust is essentially a derivative of C++ when compiled to binary, which does not really make it a strong competitor for plain #C. It can substitute C in many cases for sure, just like C++ did, but there’s always need for minimal systems programming language, which also looks elegant in binary, not just in source code.
A compiled C program can be quite easily understood with a binary with no debug symbols at all if you understand the CPU architecture well enough. That is, and will be a strong asset for C.
I'm doing a lot of Blender -> Bevy work at the moment, and I needed a way to visually check the resulting texture atlases. Hence this sprite viewer that pulls in the metadata I'm generating via python scripts and Blender.
bevy_inspector_egui on a Resource + the generated information and I can check the animation for any directionality and any animation.
It's often good if secrets are redacted in logs: This avoids accidental publication of a user PIN (or decrypted payload) in bug reports.
On the other hand, it can be useful for a developer to have full and verbatim logs (including secrets) for debugging.
We started work on this, but would like to hear from you. What should we do?
I wrote an overview and sales pitch for #RustLang for my new website: https://www.ncameron.org/rust/ What do you reckon? Does it tell you what you'd need to know if you're curious about Rust, but don't know much about it?
If Cargo gained a [diagnostics] table to mirror the recent #[diagnostic] attribute, what use cases would you have for improving Cargo errors related to your packages?
Updating crates.io index
error: failed to select a version for the requirement `bindgen = "=0.69.4"`
candidate versions found which didn't match: 0.65.1, 0.64.0, 0.63.0, ...
If I run crate search bindgen, it shows that v0.69.4 clearly exists.
nother page up on the website, and perhaps the most interesting one: #RustLang training courses! https://www.ncameron.org/training/ There's a bit of detail about the courses I'm planning to offer and I'm really interested to hear what you all think about them (and of course any thoughts on the website design - this is the busiest page yet).
🎉 We have news: We've updated #Ferrocene to #RustLang 1.76.0 and you can now purchase your license online in our shop. @pietroalbini fills in the details over on the blog 👉
»Prusti is an automated program verifier for Rust, based on the Viper infrastructure. It leverages Rust's strong type guarantees to simplify the specification and verification of Rust programs.«
Do any of you know this and use it or are there "better" or even integrated tools for this, if such a thing is needed at all?
Last Friday we had our 4th virtual @bevy meetup, let's say thank you to the amazing speakers: François, Lorenz and Jos - in case you want to (re)watch it here is the recording: https://youtube.com/live/rnE_nINEs2M - #rustlang#gamedev 🦀🎮