@diyelectromusic, since you're into embedded tech and microcontrollers, you may appreciate this one.
It's a Real-time Operating System kernel I wrote in C and Assembly for AVR chips. My intent was to learn about how operating systems interface with hardware.
I'd like to rewrite it with #Rust and finish the task scheduler.
Hmm… I guess I could probably write a blog post about how my quest to speed up regexp matching in a #ruby Rake task led me eventually to #rustlang and how it worked in the end… 💎🦀🤔
So now that -Zcheck-cfg is stabilized and enabled by default, there's no way to tell the compiler about custom cfgs other than a build script?
I routinely use a custom cfg for rustdoc so that I can use nightly features when publishing (both with docs.rs and CI). #[cfg(coverage)] is also used in some places.
Apparently spurious warnings are extremely wide-spread, so I'm not clear on why this was stabilized with such a glaring hole in it.
I came across this article the other day, titled “Why Rust cannot replace C++”.
I feel that the author completely fails to understand the opposing argument. The article claims that with “new” C++ features like smart pointers, you can write safe code in C++, therefore Rust is unnecessary.
But I don’t want a language where I can write safe code, I want a language where I must write safe code.
Sure, it’s much easier to pass pointers (*, &, or shared_ptr) around, but now I have the “cognitive overhead” of ensuring that it’s only accessed from one thread at a time. Or not used after it’s been freed in the former cases.
When I’m working with the borrow checker that is something that I don’t have to think about. It’s less “cognitive overhead”.
There’s this common statement that “the cognitive overhead of working with the borrow checker just isn’t worth the security benefits when you can write safe code in other languages”.
But the comparison is always to the “cognitive overhead” of writing something in some other language. When the comparison should be to writing something correctly in some other language.
Rust references and borrowing rules: 😵💫
Rust references and borrowing rules for closures where there are different types of closures based on what/how they borrow and give back: 😵💫😵💫😵💫 #rustlang
This week in Bevy we've got some project changes relating to contributing, PR review, and the formalization of working groups, new color grading and state-management features, as well as some exciting experiments and demos.
Particularly interesting on the experimental side of things is a new crate and some experimentation with Bevy/Vello integration.
This was tried a couple of years ago, but there some issues with mingw - so kudos to the folks that investigated and fixed those (sorry that I don't have links)!
Next step, the MSVC builders, which will require bumping the version of Clang that's used to build LLVM first...
In the last year and a half I have written a lot of Rust code, only some of which is open source at the moment: Xot, the capable XML tree library.
I have also most of a XPath 3.1 implementation and part of an XSLT 3.0 implementation. And a structural human readable diffing library for XML documents.
I happen to have a (revived) background in established tech like XML and I can write Rust, which makes for an interesting combination.
oct-git focuses exclusively on ergonomic use with OpenPGP card-based signing keys
It is designed to be easy to set up, standalone (no long running processes), and entirely hands-off to use (no repeated PIN entry required, by default). It comes with desktop notifications for touch confirmation (if required)