Possible Rust

It’s possible in Rust to conditionally implement methods and traits based on the traits implemented by a type’s own type parameters.

Rust supports a number of type coercions, which implicitly convert one type to another.

You may not know this, but it’s possible to give names to your lifetimes which are longer than a single character!

Trait objects are Rust’s usual mechanism for dynamic dispatch, and when they work they’re wonderful, but many Rust programmers have struggled with the question of when a trait can become a trait object, and what to do when a trait they’re using can’t.

Rust functions are surprisingly diverse, sitting at the intersection of multiple language features which may take time to understand.

Steve Klabnik recently wrote about whether out parameters are idiomatic in Rust.

Rust gets a lot of first impression posts.

Foreign Function Interfaces (FFI) are a core mechanism for enabling integration of new languages into existing codebases or building on existing libraries.

Rust has two major mechanisms for delegating logic: enums and trait objects, and it may be unclear when to use one or the other.

The Rust compiler ships with a number of useful lints on by default, and many use Clippy to provide additional lints.