po4yka/rust-skills / skills/rust-callback-bounds
rust-callback-bounds
VerifiedUse when choosing or repairing the bound on a callback parameter or a stored callable — Fn(&T) -> K, a for<'a> HRTB, a sort_by_key key projection, or a struct field that holds a closure (generic F, Box<dyn Fn>, fn pointer field). Triggers on "lifetime may not live long enough" from a closure, "one type is more general than the other", "borrowed data escapes outside of closure", "callback returns a reference", "store a closure in a struct", "function item types cannot be named directly", E0747, E0562, or "reached the recursion limit while instantiating".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.6 KB |
| references/closure-capture-semantics.md | markdown | 7.1 KB |
| references/hrtb-diagnostics.md | markdown | 8.7 KB |
| references/key-projections.md | markdown | 2.6 KB |
| references/storing-callables.md | markdown | 21.5 KB |
references/key-projections.md
View on GitHub# Key projections and generic callback outputs
Deep material for [SKILL.md](../SKILL.md). Read only the section that matches the task.
- [Change what the callback receives](#change-what-the-callback-receives)
- [Generic outputs need RPITIT or a GAT](#generic-outputs-need-rpitit-or-a-gat)
## Change what the callback receives
Before you build a projection DSL, change what the callback is handed. These both compile with
the very projection `Vec::sort_by_key` rejects:
```rust
struct Order { country: String, code: u32 }
fn main() {
let v = vec![
Order { country: "cz".into(), code: 3 },
Order { country: "at".into(), code: 1 },
];
// v.sort_by_key(|o| &o.country); // would NOT compile
let m = v.iter().max_by_key(|o| &o.country).unwrap();
assert_eq!(m.code, 3);
let mut refs: Vec<&Order> = v.iter().collect();
refs.sort_by_key(|o| &o.country);
assert_eq!(refs[0].code, 1);
}
```
For an iterator of `&'s T` the closure parameter is `&'x &'s T`. `&o.country` reborrows through
the inner `&'s T` and yields `&'s String`, whose lifetime the collection fixes, not the callback
binder. The higher-ranked `'x` never reaches the output, so a fixed `K` is satisfiable.
`Vec::sort_by(|a, b| a.country.cmp(&b.country))` is the third escape and needs no new type at
all. Reach for it before any of the trait machinery below.
## Generic outputs need RPITIT or a GAT
A composite your signature can name still fits a higher-ranked `Fn` bound.
`impl for<'a> FnMut(&'a T) -> Reverse<&'a str>` and `impl for<'a> FnMut(&'a T) -> (&'a str, u32)`
both accept a bare closure. Reach for a trait only when the output must stay a type *parameter*,
because no `Fn` bound can write `-> K<'a>`. `impl FnMut(&T) -> impl Ord` is rejected:
``error[E0562]: `impl Trait` is not allowed in the return type of `Fn` trait bounds``. Declare a
one-method trait with `fn project<'a>(&mut self, i: &'a In) -> impl Ord + use<'a, Self, In>`, and
have callers pass a named unit struct instead of a closure. That loss of the closure is the cost
of this row. `use<..>` in a trait method needs Rust 1.87, and it is load-bearing: without it the
result also captures the `&mut self` borrow, and two calls in one comparison fail with E0499.
Read [storing-callables.md](storing-callables.md#composite-outputs-rpitit) when you
write this trait. It has the runnable examples and three traps: repeat `impl Ord + use<..>` in
the impl (a concrete type triggers `refining_impl_trait`), keep the lifetime off the trait
(`for<'a> K: KeyProjection<'a, T>` breaks on a borrowed `T`), and use a GAT `type Out<'a>` when
callers must name the output.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |