Pyry Jahkola

Other possible naming options: `ascendingElements`/`descendingElements`, or `increasingElements`/`decreasingElements`. I think the former of these two could go better together with the Foundation type `ComparisonResult` with its cases `orderedAscending` etc.

> Another option is to have priority getter as field: > > ```swift > struct Heap { > var priority: (T) -> U > ... > } > ``` >...

> In this implementation there is no difference between keypath or order function in Equatable conformance. More importantly, I think you just proved that `Equatable` conformance is hardly even useful....

Wouldn't a name as straightforward as `changes` be to the point for this purpose? Immediately conveys the idea of comparing successive values only.

> Could you do me a favour an try to write a validation test that represents what currently is not working like you expect it to work. Let me help...

I'm sorry @Kolos65, but I think there is a bug in that. Throttle should reset its timer for each _output_ it yields, not input. If the timer lapses without further...

AFAICT this is a key component in reducers which inject a projection of their state or action as dependencies for their children, so a much needed building block. Yes please!

@acosmicflamingo One example could be letting child features know the currently logged in user via `@Dependency(\.currentUser) var user: User?`, something like: ```swift ReducerReader { state, _ in withDependencies { $0.currentUser...

> […] `ScrollViewReader` and `GeometryReader` have a totally different purpose than `ReducerReader` as they give you a specific lens as to what's going on **inside** their content which you could...

> I've read this a couple of times, but I still can't figure out how this differs from a normal reducer, is there a short explanation of that? It gives...