Post

You should still care about modularity, even if you don't write modular code yourself. Because modularity allows you to reuse modular code written by *others*, so that you can write much less non-modular code yourself. #CGP #RustLang

#1 text-overflow: ellipsis; hater

@nekotachi.bsky.social

12 Jan 2025

my question is why we need a new paradigm to write modular code when we've been doing a pretty good job of it anyways? couldn't we just have more trait-only crates, similar to serde?

Context-Generic Programming

@contextgeneric.dev

Good question! The problem is it is not possible to define multiple context-generic implementations of a trait in Rust, due to limitations of the trait system. CGP is a workaround of that limitation. In CGP we make heavy use of trait-only crates, such as cgp-error, perhaps more than normal Rust.

12/1/25, 10:01 am0 reposts0 likes

Context-Generic Programming

@contextgeneric.dev

12 Jan 2025

As an example, you can't write a generic `Serialize` implementation that works for any type that implements `Display`. But you can do that with CGP, if there a corresponding providder trait like `SerializerProvider`/

#1 text-overflow: ellipsis; hater

@nekotachi.bsky.social

12 Jan 2025

so it's basically a workaround to coherency rules, allowing multiple blanket impls?

Context-Generic Programming

@contextgeneric.dev

12 Jan 2025

Yup, you can think of it that way. Though if we just remove coherence alone, there are other problems popping up that makes programming in it less ergonomic. So CGP also has other techniques that work together *with* coherence to make it easy to choose and wire up different blanket impls.