Learning new things!
Parallelism in Rust usually means one of three things:
When making things go parallel, there are following things to consider. Safe parallel code comes from being …
A procedural macro is Rust code that runs at compile time and generates Rust code by programmatically transforming syntax trees.
Normal Rust code runs at runtime
Procedural macros run while the compiler is compiling
Every value in Rust has exactly one owner at a time, and when the owner goes away, the value is automatically cleaned up.
Let’s build this step by step.
Rust enforces these at compile time:
What it is
T: Trait, impl Trait)How it works
follow the instruction in this video
…
This post collects the concepts people mentioned for different programming languages, so I can understand what they are talking about.
ownership,
lifetimes,
memory safety
Tokio
async await,
event driven Rust systems
asynchronous programming and concurrency patterns
template meta-programming, SFINAE, RAII, constexpr,
multithreading, web protocol (e.g. websocket, RESTful)
event-driven …
“Standard” comes from the Unix philosophy (“standard streams”).
Every program automatically starts with three built-in streams:
| Name | Abbrev | FD | Meaning |
|---|---|---|---|
| Standard Input | stdin | 0 | Where the program reads input |
| Standard Output | stdout | 1 | Normal program output |
| Standard Error |
Computers only store bits — 0s and 1s.
To represent both positive and negative integers, they use two’s complement encoding.
It’s called two’s complement because you take the binary complement (invert all bits) and then add 1.
invert all bits -XOR 1
I want to understand:
how cargo run -r --bin powdr_openvm -- ... works and how you can trace back CLI parameters like --input and --autoprecompiles to the source code.
chatGPT said I need to check [bin] definition in Cargo.toml to get what binary will be, but there is no [bin] …
Start with the overview to understand …