r_rust🦀

I translated The Rust Programming Language into Roman Urdu I recently finished translating the complete The Rust Programming Language (Rust Book) into Roman Urdu, including all the appendices. I started this because many developers in Pakistan and India are more comfortable reading Roman Urdu/Hindi than technical English. My goal was to make the Rust Book easier to approach without changing the technical content. The translation is available here: https://github.com/Fakhir-Israr-200219/rust-roman-urdu Hopefully it can be useful to Roman Urdu, Urdu, and Hindi readers who are learning Rust. https://redd.it/1wygk5b @r_rust

An experimental research engine for multi-layer network stack fingerprinting in async Rust This post documents an ongoing technical study on protocol-level traffic analysis and upstream signature orchestration. The primary artifact of this research is a domain-agnostic inspection engine engineered to manipulate client heuristics across the TLS, HTTP/2, and TCP layers simultaneously. Traditional implementations in this domain often rely on static, monolithic browser emulations that lack dynamic parameter control. To address this limitation, the engine utilizes a declarative profile architecture, allowing granular configuration of transport and application layer metadata - including cipher suite ordering, ALPN negotiation, SETTINGS frame sequencing, pseudo-header layout, and SYN option rewriting via Linux NFQUEUE/iptables. From a systems engineering perspective, implementing this in Rust presents specific design and architectural challenges: State & Concurrency Management: Propagating unified profile state across asynchronous `Tokio` streams while ensuring zero-copy socket IO and precise handshake characteristics. Low-Level TLS Orchestration: Interfacing with BoringSSL (via btls/tokio-btls) to expose internal TLS stack parameters (e.g., extension ordering, GREASE values, and ECH setup) without breaking memory safety guarantees or incurring high runtime abstraction overheads. OS-Level Packet Interception: Managing kernel-to-userspace queue backpressure and handling raw network packet mutation for SYN fingerprints (TTL, MSS, window size/scale) alongside application-level stream multiplexing. Systemic Decoupling: Decoupling the network logic from execution platforms, ensuring that protocol manipulation is evaluated on its technical merits as a systems-level networking problem rather than being reduced to high-level application tropes. The underlying codebase serves as an open platform for network privacy analysis, transport layer diagnostics, and protocol mechan

STM32H7 flashing but nothing happening on the board Good morning, I am using probe-rs to flash a blinky program onto my STM32H7. It builds and flashes ‘fine’ but i don’t get any output from the board and the led does not blink. When i run the same example for the stm32f411 it flashes fine and i get text output as well as the led flashing. The program is just the example from embassy-rs and below is the important parts of my cargo.toml: ‘’’ embassy-stm32 = { version = "0.6.0", features = ["defmt", "stm32h7r3z8","memory-x", "time-driver-tim4"\] } embassy-executor = { version = "0.10.0", features = ["platform-cortex-m", "executor-thread", "executor-interrupt", "defmt"\] } embassy-time = { version = "0.5.1", features = ["defmt"\] } cortex-m = {version = "0.7.7",features=["critical-section-single-core"\]} cortex-m-rt = "0.7.3" embedded-hal = "1.0.0" build = [ { target = "thumbv7em-none-eabihf" } \] ‘’’ I am running this command: 'probe-rs run --chip stm32h7r3z8’ right now I am suspicious of memory-x but im not sure because shouldn’t it fail to flash if this is the case? https://redd.it/1wy4eps @r_rust

ClearConfig for Rust — sharing my first Rust library 🎉 https://crates.io/crates/clear-config https://redd.it/1wyqgci @r_rust

A Fond Farewell To Three Rust Foundation Colleagues - The Rust Foundation https://rustfoundation.org/media/a-fond-farewell-to-three-rust-foundation-colleagues/ https://redd.it/1wyrbf5 @r_rust

Two issues of rust regarding web ( axum for example ) I am a big fan of rust But there are two issues that need to be resolved 1- Rust ecosystem is less mature than for example go ( i know go is specialized for networking and an easy lang ) . 2- No implicit DI which would make testing easier. https://redd.it/1wyqb4i @r_rust

Rust Glancer 0.3: new trait solver and other goodies https://rust-glancer.github.io/blog/0-3-0/ https://redd.it/1wv3m6b @r_rust

I analyzed 200 Rust job postings from the last 3 months. Here's what the data says Hello there, I'm George from getarustjob.com I run a Rust-only job board and I've manually reviewed every listing that went up since July. That's 203 roles from 166 companies. I pulled everything into a spreadsheet to see what the Rust job market actually looks like, past the "is Rust getting jobs yet?" threads. 1. It's a senior market Senior: 58% Mid-level: 31% Staff / Principal / Lead: 7% Junior + Intern: 5% (10 jobs total) Of the 109 listings that state years of experience, the median ask is 5 years (middle 50%: 4 to 7). If you're trying to break in, the honest read is that hardly anyone hires juniors straight into Rust. The usual path is getting hired for C++/Python/Go at a company that uses Rust, then moving onto the Rust team. 2. Salaries (USD, annual, posted ranges only) All listings: median $171K, middle 50% $131K – $210K (n=78) United States: median $193K, middle 50% $158K – $221K (n=56) US Senior: median $198K, middle 50% $178K – $228K (n=34) US Mid-level: median $165K, middle 50% $147K – $194K (n=16) United Kingdom: median $146K, middle 50% $110K – $199K (n=7) Europe (all): median $127K, middle 50% $84K – $193K (n=17) Going from mid-level to senior in the US is worth about $32K at the median. 3. Remote doesn't mean a pay cut (in the US) US remote median: $189K (n=18) US hybrid/on-site median: $193K (n=41) That's basically the same. The catch is supply: only 37% of listings allow remote. The other 63% are hybrid or on-site. 4. US employers publish salaries. European ones mostly don't US listings with a salary range: 61% European listings with a salary range: 26% That's pay transparency laws (CA, NY, CO, WA) at work. It also makes the European numbers above much less reliable, so treat them as rough. 5. Where the jobs are United States: 45% of listings United Kingdom: 12% Germany: 7% Canada: 5% Then Poland, Netherlands, Switzerland

Hey Rustaceans! Got a question? Ask here (41/2026)! Mystified about strings? Borrow checker has you in a headlock? Seek help here! There are no stupid questions, only docs that haven't been written yet. Please note that if you include code examples to e.g. show a compiler error or surprising result, linking a playground with the code will improve your chances of getting help quickly. If you have a StackOverflow account, consider asking it there instead! StackOverflow shows up much higher in search results, so ahaving your question there also helps future Rust users (be sure to give it the "Rust" tag for maximum visibility). Note that this site is very interested in question quality. I've been asked to read a RFC I authored once. If you want your code reviewed or review other's code, there's a codereview stackexchange, too. If you need to test your code, maybe the Rust playground is for you. Here are some other venues where help may be found: /r/learnrust is a subreddit to share your questions and epiphanies learning Rust programming. The official Rust user forums: https://users.rust-lang.org/. The unofficial Rust community Discord: https://bit.ly/rust-community Also check out last week's thread with many good questions and answers. And if you believe your question to be either very complex or worthy of larger dissemination, feel free to create a text post. Also if you want to be mentored by experienced Rustaceans, tell us the area of expertise that you seek. Finally, if you are looking for Rust jobs, the most recent thread is here. https://redd.it/1wz6a3m @r_rust

Compiling the kernel with gccrs | lwn.net https://lwn.net/Articles/1095553/ https://redd.it/1wz3fq2 @r_rust

Proving Rust Web Application Correctness with Lean 4 https://medium.com/@Koukyosyumei/proving-rust-web-application-correctness-with-lean-4-8889583f1e15 https://redd.it/1wz7q4o @r_rust

Burn 0.22.0 Release: Towards 1.0, with Generic-Free APIs and Near-Instant Recompilation It's been five months since our last release, which is longer than usual, but it's on purpose. During the last four years, we took great care not to change the APIs too much, while collecting your feedback on what could be improved. Instead of spreading those changes over many releases, we bundled them into this one, so you only have to migrate once. This makes Burn 0.22 our biggest release yet, and the one we're most proud of. The API is now much closer to what we want for 1.0. As a reminder, Burn is a Tensor Library and Deep Learning Framework for both training and inference. Generic-Free APIs Since the beginning, Burn has been built around the Backend trait, with features like autodiff, kernel fusion and remote execution implemented as backend decorators. This is still the case, and they all compose well together. What changes is that user code doesn't carry the backend generic anymore. Models are plain types, and the device selects where and how they run: #derive(Module, Debug) pub struct Model { linear: Linear, } let device = Device::cuda(0); // Device::wgpu(..), Device::flex(), ... Removing the generic from user code breaks the dependency chain that the compiler had to go through every time you edited a model. The result is near-instant recompilation after a model edit (numbers in the table below). There's another big change under the hood: most of the stack is now pure Rust. Pliron replaces MLIR, native compilers replace transpilers to CUDA/HIP, and Turso replaces a bundled SQLite. That means fewer bundled C and C++ dependencies to build, and a pipeline you can read, debug and patch in the language you already use. The first clean build takes a bit longer as a result, and it's a trade we're happy to make. Going All-In on CubeCL When we started, we relied on existing libraries for performance, with backends for ndarray and LibTorch. Over

to cover them. Don't hesitate to skim it, and refer to the migration guide for upgrading. A lot of this release came from your issues, PRs and questions on Discord. Thank you. Link: https://tracel.ai/blog/release-0.22.0/ https://redd.it/1wzc0sj @r_rust

Hardware-Aware Programming in Rust https://medium.com/@alan0408yuan/hardware-aware-programming-in-rust-6e68a70c1535?postPublishedType=repub https://redd.it/1wzj1sb @r_rust

1.99.0 miscompilation with FFI bool return type on x86_64 https://github.com/rust-lang/rust/issues/163911 https://redd.it/1wzn34d @r_rust

The TokioConf 2027 CFP is open https://tokio.rs/blog/2026-10-06-tokioconf-2027-cfp https://redd.it/1wzcnh0 @r_rust