request-for-explanation / podcast
The Request for Explanation podcast that explains Rust RFCs
☆59Updated 4 years ago
Alternatives and similar repositories for podcast:
Users that are interested in podcast are comparing it to the libraries listed below
- cargo-safety provides safety checks for Rust projects by finding all uses of unsafe code in dependencies.☆62Updated 7 years ago
- A fuzzing tool for incremental compilation that walks git history☆32Updated 6 years ago
- Convert `try!()` into `?`s☆34Updated 7 years ago
- A real-time hierarchical profiler☆81Updated 8 years ago
- Non-lexical lifetimes RFC.☆48Updated 6 years ago
- Scary macros for serde_json☆43Updated 8 years ago
- Core functionality for handling rustc's save-analysis data☆40Updated 6 years ago
- In support of measuring heap allocations in Rust programs.☆100Updated 5 years ago
- Safely combine results☆81Updated 6 months ago
- A composable wait system.☆76Updated 6 years ago
- And I'll look down and whisper "GNO."☆59Updated 8 years ago
- Custom derivation macro for Rust☆112Updated 7 years ago
- Test the downstream impact of Rust crate changes before publishing☆58Updated 6 years ago
- Derive for the Display trait☆51Updated 6 years ago
- bytevec: A Rust serialization library that uses byte vectors☆41Updated 2 years ago
- Stateful, a Rust Control Flow Plugin☆107Updated 7 years ago
- Cargo subcommand for contributing to your dependencies☆56Updated 5 years ago
- The core `Service` trait in Tokio and support☆82Updated 6 years ago
- ☆97Updated 8 years ago
- Linting your rust project with clippy as a service☆36Updated 4 years ago
- Initial rallying point for ideas and PRs around solving discoverability of Rust crates for production use.☆29Updated 8 years ago
- Tutorial and demo of rust compiler replacement tooling☆56Updated 4 years ago
- A small Rust library for recycling types with owned memory☆33Updated 9 years ago
- cargo clippy☆69Updated 8 years ago
- See instead assert_cmd☆148Updated 6 years ago
- Amazing documentation tooling for Rust☆152Updated 6 years ago
- Cheat sheet for concepts in Rust which come in matching sets or have some pleasing symmetry☆69Updated 7 years ago
- A `#[safe]` attribute for explaining why `unsafe { ... }` is OK.☆81Updated 5 years ago
- Compile time stack traces for Rust errors (no backtrace!)☆74Updated 6 years ago
- A reader-writer lock that can be used with a Condvar.☆29Updated 8 years ago