Dirkjan Ochtman

Yeah, it's niche enough that I don't have much time to spend on it. I think there are other mechanisms in Askama that help with code re-use and can probably...

A `for` loop always calls `into_iter()` on its `Expression`. If the template calls `iter()` on it, the resulting type should already be an `Iterator` and so calling `into_iter()` on that...

Why not just call a method on the context type instead?

I feel like this is pretty niche - it feels reasonable to me that filters are stateless - and I don't find the proposed configuration API very compelling. Seems likely...

This broadly makes sense to me, and I think I prefer the `block` name over `partial`. @vallentin @Kijewski what do you think? Does this fit with Askama's design? Will it...

I think I'd also be fine with these limitations as long as they cause compile-time errors; then it's sort of at the author's peril. I don't think there is a...

On the other hand, this seems like a really nichey feature since we already have includes and macros...

> That is certainly true. Technologies like htmx are new and not widely known in the Rust community. I mean, this is essentially a way of doing functional reactive programming...

Can you write up a more specific example of what you're looking for?

Oof, `{% when (Some, Some) with (a, b) %}` looks pretty ugly, not to even speak of `{% when (Some, None) with (a, _) %}`. I'm not sure something like...