https://github.com/ferrous-systems/rust-exercises/ https://github.com/ferrous-systems/rust-training/ https://play.rust-lang.org https://manishearth.github.io/blog/2015/05/17/the-problem-with-shared-mutability/ https://ferrous-systems.com/blog/testing-proc-macros/
3/24/2025We would like to improve the state of inspecting Rust projects at runtime. Currently, this fields is fractured and logs coherence. This is preferably done by reusing existing methods and libraries, but also with some substantial own development. Observability describes the ability to gather data about the runtime from a program, often to monitor its current behaviour. It can also be used during development though, e.g. for debugging. Our thesis is: all tasks to gather runtime information about programs often boil down to a base number of techniques and could be improved if the whole stack cares about such tasks. What to observe at runtime? Business events, such as a new client arriving High-level events, such as a task resuming or yielding, descheduled, etc. Similar, for threads
2/10/2025View the slide with "Slide Mode".
6/27/2024Rust is great for writing async code. But what async code should you write? This workshop will take this question and introduce you to basic async patterns and how to apply them in Rust. It will guide you through async programming concepts and give you a glimpse into constructing larger, concurrent applications out of the basic elements. It will introduce you to tasks, how they apply to threads, evented IO and how Rust manages all the hard bits. Other topics include async testing and how to come up with new, high-level abstractions. Workshop contents: The basic model of async in Rust: Futures, Tasks, async/.await How this model applies to libraries like tokio How to use building blocks like tasks and channels to build reactive systems
3/13/2024