
Collection of universal hashing functions in Rust:
Collection of universal hashing functions in Rust:
Tired of race conditions and manual lock management in C++? Here's how Rust makes this problem disappear entirely: https://col.la/rustc3#rust #rustlang #coding#softwareengineer
I think there is a Dunning–Kruger like effect whereby the complexity of rewriting an open source project from scratch is vastly underestimated the less you know about the scope of the work.
You could make 80% of #inkscape in a couple of months of javascripting. But this is 80% of Inkscape's surface. Not actual depth.
Rewrite it all in #Qt? #React? #JS? #Rust? These are ideas aren't bad. But they are vast projects that would cost millions of dollars.
Related to: https://mastodon.uno/@maxdid/114691504835360868
Heck yeah, this thing will blow up!
Introducing Operese (a Windows-to-Linux migration tool made by a nerd):
https://yewtu.be/watch?v=PMoXClh8emw
(or YT: https://www.youtube.com/watch?v=PMoXClh8emw)
The demo is very impressive! 👀
It apparently migrates your #Windows10 installation to #Linux #Kubuntu (❤️) with all your files ready to use. 🚀
Written in #Rust, but not yet #OpenSource (according to author will be Open Source in the near future).
Also cool:
https://probe.rs/docs/
This is cool:
https://crates.io/crates/cortex_m_microclock
Owi
https://github.com/OCamlPro/owi
Symbolic execution for #Wasm, #C, C++, #Rust and #Zig
"#Owi is an open-source framework for advanced #WebAssembly analysis and manipulation, with a focus on practical symbolic execution and robust tooling. It is designed for researchers, engineers, programming language enthusiasts and practitioners requiring precise, flexible, and extensible support program reasoning."
#FormalVerification#SoftwareTesting#Testing#SoftwareEngineering #RustLang#ZigLang
In case anyone wants to try this in #Rust:
F yeah, my #STM32F3DISCOVERY board arrived! The Embedded #Rust Book, here I come!
Specifically, I mean something like this (this is part of the blake3 API that I want to match):
/// A generic array with better ergonomics?
pub struct GenericHash<const N: usize> {
value: [u8; N],
}
impl<const N: usize> GenericHash<N> {
pub fn as_bytes(&self) -> &[u8; N] {
&self.value
}
pub fn from_bytes(value: [u8; N]) -> Self {
Self { value }
}
}
Today it crossed my mind for the first time that, after all, I don't need #typescript at all.
Some months ago, after some months spent with #rust I got to a compromise idea that I should use #rust for "serious" tasks, and #javascript for quick modelling. The idea evolved quickly into it's same form, but with #typescript in place of JS.
Two months later I'm failing to get #deno run my software because the network layer won't work if I import some .ts file of mine; if only I knew which one.
Variadic Generics ideas that won't work for #Rust - by Olivier Faure (aka poignardazur)
https://poignardazur.github.io//2025/07/09/variadic-generics-dead-ends/
"After years of design discussion, we’re finally at a stage where variadic generics are reaching the top of the triage pile. Serious discussion and initial work is, hopefully, about to start. I’m hoping this article helps us not get dragged down in litigating the same alternatives over and over again."
Me, when I see variadic generics: 🤯
The #Rust #compiler #performance #survey 2025 only runs until next Monday, 7th July - so fill it if you haven't yet and help the Rust project make us Rust developers more productive! 🚀
https://blog.rust-lang.org/2025/06/16/rust-compiler-performance-survey-2025/
A space for Bonfire maintainers and contributors to communicate