I like to minimize the size of binaries I build. Unremovable debugging strings annoyed me, so I've added an option to completely neuter `Debug::fmt` in #Rustlang
I'd like to propose a new option that makes #[derive(Debug)] generate no-op implementations that don't print anything, and makes {:?} in format strings a no-op.
There are a couple of motivations fo...
The Rust Foundation is an independent non-profit organization to steward the Rust programming language and ecosystem, with a unique focus on supporting the set of maintainers that govern and develop the project.
New blog post: on that time when I decided that if being able to panic one Rust program is good, then a feature that lets you panic _other_ programs would be better, right?
No, really, it's awesome. Here's Hubris's oddest syscall.
today I've heard for the first time about the #RigelA open-source screen reader project for #Windows written in #RustLang. Unfortunately only Readme has an English version, all other documents and code comments are in chinese, but the project seems very promising. Use Google Translate or another translator if you, like me, don't speak Chinese. https://gitcode.net/mzdk100/rigela
If I wanted to incentivize people to try and exploit Hubris, what should I do? What would you want to see?
While open source, the system is mostly used by Oxide, a for-profit company, so I would expect "am I doing this for free" to come up. Explicit threat model is also good. What else?
We've hired firms for this but with mixed results (they mostly know C). I wanna open it to everyone else. I would be _delighted_ to give guidance.
So Hubris on stm32 has a task called "sys" that handles a lot of common shared peripherals, like GPIO and clocking and reset.
One of the challenges on Hubris is that _parts_ of your application (like sys) can crash, and the other parts need to figure out how to deal with that.
Well, as of this afternoon, sys can't. As in, I have squashed the last potential panic, and turned on a switch that makes new panics into build errors.
What if #rustlang only had panic="abort"? (Instead of panic="unwind", today's default.) It could simplify some parts of the language and prevent subtle bugs.
Do you absolutely need catch_unwind? If yes, please leave a reply!
(Panic hook and backtrace etc. will still work of course!)
With the upcoming stabilization of the diagnostic namespace, I want to take stock of the compile time error messages generated by diesel and see what messages can be improved.
Diesel is known for sometimes generating sub-optimal compile time error messages. With the upcoming stabilization of the #[diagnostic] attribute namespace and the #[diagnostic::on_unimplemented] at...
This project needs more/new maintainers. I took over maintainership in 2019 (IIRC) during a project at my employer back then, because I needed fixes/changes in this crate to fulfill my task at work...
A few weeks ago, I introduced and fixed a bug where I accidentally checked if a string literal, instead of a vector, was empty, jokingly saying that I blamed Clippy for not having a lint against it. Following a suggestion from @zeenix, I created a feature request, and it's now actually implemented. This means that Clippy will now warn you if you try to call `is_empty` on a string. https://rust-lang.github.io/rust-clippy/master/index.html#/const_is_empty
> add LLVM CFI and cross-language LLVM CFI (and LLVM KCFI and cross-language LLVM KCFI) to the Rust compiler as part of our work in the Rust Exploit Mitigations Project Group. This is the first cross-language, fine-grained, forward-edge control flow protection implementation for mixed-language binaries that we know of.
We’re pleased to share that we’ve worked with the Rust community to add LLVM CFI and cross-language LLVM CFI (and LLVM KCFI and cross-language LLVM KCFI) to the Rust compiler as part of our work in the Rust Exploit Mitigations Project Group.
Does anybody have a good idea how one can verify that your rust compiler and the FFI code you interact with use the same libc?
Some of our rust code inside mesa will allocate/deallocate code indirectly via `malloc`/`free` and I don't think we really want to mix and match across different libc impls here.
So we want to figure out at configure or compiler time that everything uses the same libc.
The new GStreamer 1.24 release is also the first that has a Rust component as part of core, in addition to all the plugins that were already part of previous releases.
Over the last months the Rust/cargo support in meson improved a lot.
It's now ready to build and install a GTK4 Rust application with around 70 dependencies without having to write almost any custom build glue for the dependencies.
The application in question is just a small experiment of mine for rayon and GTK4 input handling / rendering. The more or less same should work for other GTK4 applications at this point.
All this still depends on two unmerged meson PRs, but it's a huge step forward from the situation just a few months ago.
I hope in the future this will allow GNOME applications written in Rust to have a less strange and fragile build setup than what they have right now with mixing cargo and meson.
Relatedly, I also released rpgpie 🦀️🔐🥧 v0.0.1 (https://crates.io/crates/rpgpie), an experimental high level OpenPGP API based on rpgp (rsop is built on top of rpgpie).
Hm...I'm getting the impression that #Rust is increasingly met with a refusal by some people (it's an almost _hateful_ attitude sometimes).
I wonder why. Of course there are a lot of layers to it, but one is definitely that Rust has gotten a lot more exposure to people and so there are just a lot more potential `match`es that lead to Err(()) and that's Ok(()) (sorry, pun intended).
But I wonder, if there's more to it than what meets the eye (feeling excluded/alienated/left behind?).
#rustlang is coming into @thunderbird now too! I loved Thunderbird back in the day but--as acknowledged in this talk--it has fallen behind its competitors over time. Excited to see it gaining ground again!
What it does This lint would warn against using try_into from the TryInto or TryFrom trait when there is an available Into or From implementation. Advantage Remove the need for handling an error ca...
I mistyped cago instead of cargo and now I want to either unlearn Spanish or unsee my typo. That's a worse typo than both gst-insect-1.0 instead of gst-inspect-1.0, and gst-lunch-1.0 instead of gst-launch-1.0.
None of the major Rust web frameworks have a great error reporting story. We try to implement robust error logging with both axum and Actix Web and then compare the results with Pavex, an upcoming Rust web framework.
My reaction when I discover a meson.build script running "cargo build" in the repository of the first example program I opened from the ones listed on the gtk-rs documentation page.
Is this common in the rust world when interacting with primarily C based libraries?
Have you ever tried to compile a helloworld Rust program in --release mode? If yes, have you seen its binary size? Suffice to say, it’s not exactly small. Or at least it wasn’t small until recently.
#Hugo's slogan of being "The world’s fastest framework for building websites" is a shameless lie.
It has been raised up 3 times on Github with benchmarks showing that other full-featured static site generators like #Zola (#Rust) are faster, sometimes by 10x. Each time, the issue is closed and locked.
I migrated a couple of websites from Hugo to Zola and won't look back.
Feel free to ping me if you need any help with Zola 🥰
We have just issued the first #release of #sshd-openpgp-auth and #ssh-openpgp-auth.
Using this server and client-side tooling it is possible to manage the #authentication of #SSH host keys with the help of an #OpenPGP certificate as trust anchor.
❤️ 
🦀 
