Whether you're just getting started or ready to elevate your Rust skills, KDAB has you covered. In collaboration with the Rust experts from @ferrous, we offer both introductory and advanced Rust training courses: https://training.kdab.com/portfolio/rust/ #RustLang #Embedded #Training
Due to a misbehaving crawler taking down docs.rs three times, we now added rate limiting.
This shouldn't impact any normal user, we're happy to talk if this affects you.
Officially we follow the crates.io data policy, so crawlers should be limited to 1 request per second. Until now we didn't validate / limit that and relied on the sanity of the crawlers.
added chance-based splitters
probability indicated by the glow of the arrows
a simple use case: 'I only wanna sell 50% of the items on that conveyor'
I quite like "#[deny[clippy::unwrap_used)]", outside test code, but it does require me to break my habit of just letting code panic on unexpected conditions, instead of noticing them and returning an error.
Pitfalls of Safe Rust
https://corrode.dev/blog/pitfalls-of-safe-rust/
Discussions: https://discu.eu/q/https://corrode.dev/blog/pitfalls-of-safe-rust/
I think I found something weird & scary with `#[target_feature]`. Is this expected?
This feels like it should *at minimum* trigger a lint. How am I supposed to know whether trait impls added extra safety preconditions — especially when using `dyn/impl Trait` and/or an unsealed trait?
![pub trait Example {
unsafe fn demo(&self) {}
}
pub struct S;
impl Example for S {
// This isn't applied to the trait's fn!
#[target_feature(enable = "avx2,aes")]
unsafe fn demo(&self) {}
}
pub fn accept_dyn(value: &dyn Example) {
// SAFETY: umm ???
// Who knows what #[target_feature]
// attributes the trait impl has imposed?!
unsafe { value.demo() }
}](https://media.hachyderm.io/media_attachments/files/114/277/042/404/600/437/original/031396318ac475b3.png)
Nice new milestone for #embedded #Rust development: defmt 1.0 has been released. The crate enables logging for microcontrollers without text or number formatting on the device – instead, the device sends numbers of interned strings to the host, which composes log messages.
1.0 is not only a stable release, but also enables logging #CBOR data into diagnostic notation on the host.
Rust dev - Tauri event system for ArkSync
My article about the experience of Rust integration into a C++ code base
https://clickhouse.com/blog/rust
Discussions: https://discu.eu/q/https://clickhouse.com/blog/rust
Rust finally has trait upcasting and target_feature in stable with 1.8.6!
https://blog.rust-lang.org/2025/04/03/Rust-1.86.0.html
#rustlang #rust
@thezerobit interesting, thanks. I recently began building my first REST API so learning, learning, learning and have GraphQL on my list to look into.
No reason I can't offer both at least in the short term so your comments are welcome.
One issue I guess is the level of support, esp for a novice.
I found a actix + utoipa have helped a lot as I'm coding on a Rust backend. Do you know if there are similar tools to help with #GraphQL+ #Rustlang?
#Rust
1.86.0 released by @rust - New features: trait upcasting, HashMaps and slices indexing multiple elements mutably, safe functions marked with #[target_feature], debug assertions that pointers are non-null when required for soundness, make missing_abi lint warn by default, etc. https://blog.rust-lang.org/2025/04/03/Rust-1.86.0.html #RustLang #OpenSource #cybersecurity #software #engineering #tech
![article overview screenshot - follow link for full text
Rust Blog
Announcing Rust 1.86.0
Apr. 3, 2025 · The Rust Release Team
The Rust team is happy to announce a new version of Rust, 1.86.0. Rust is a programming language empowering everyone to build reliable and efficient software.
What's in 1.86.0 stable
Trait upcasting
This release includes a long awaited feature — the ability to upcast trait objects. If a trait has a supertrait you can coerce a reference to said trait object to a reference to a trait object of the supertrait:
trait Trait: Supertrait {}
trait Supertrait {}
fn upcast(x: &dyn Trait) -> &dyn Supertrait {
x
}
The same would work with any other kind of (smart-)pointer, like Arc<dyn Trait> -> Arc<dyn Supertrait> or *const dyn Trait -> *const dyn Supertrait.
[...]](https://files.pnw.zone/media_attachments/files/114/275/448/354/378/910/original/699999ff4b9d9bd3.png)
made another little #video about my media proxy that allows me to have my own little Youtube/Peertube on my website 
if you like #RustLang and want to come along for a quick code review, you're gonna enjoy this 
https://bram.dingelstad.works/videos/making-syrinx-my-media-proxy/
#rustlang 's new 'get_disjoint_mut' looks like it will simplify some of the previously painful Rustisms:
https://doc.rust-lang.org/stable/std/primitive.slice.html#method.get_disjoint_mut
Being a graphics noob, I was wondering why colors rendered perfectly on my Windows machine but looked off on my 10-year-old Mac. Turns out it was all about color spaces. I had to manually handle the conversion. Here’s a more accurate rendering. #rustlang #wgpu #creativeCoding #generativeArt #rendering
Rust 1.86 just released: https://blog.rust-lang.org/2025/04/03/Rust-1.86.0.html and it stabilizes trait upcasting - especially useful in connection to the Any trait #rustlang 
I'll start by posting some of my earlier progress here to catch this timeline up. I've started another round of rendering practice, this time with wgpu, and audio will be a key focus from the beginning, not an afterthought. This is the mandatory triangle! #rustlang #wgpu #creativeCoding #generativeArt
