AlexanderBollbach

I agree. I'm inheriting a project which used the old style and am clueless about how to proceed.

@JamesPerlman I find the idea of setting state and then pushing a route and then reading from the state in the next 'component' in keeping with the 'keep everything in...

@trentguillory @mjarvis i thought of another way to do this. but it would involve changing the library. looking at the source, (specifically `Router.routingActionsForTransitionFrom`), if my routing state goes from `["foo"]`...

@ianegordon curious to know what that functionality is.

yes it does seem that way. `offset` and `inset` are the same. this is very confusing and unhelpful

so i ran into this issue and incurred performance hits in my app. i called `skipRepeats` to insert a specific equality checking closure that was optimized for the specific StoreSubscriber...

@DivineDominion I think my problem can be distilled down to [this gist](https://gist.github.com/AlexanderBollbach/fd27cea9090f69d3605fbff220a9dbb8). My guess is that because arbitrary tuples aren't Equatable the StoreSubscriber isn't able to perform its default update...

@JoeCherry all tuple elements are already Equatable

say i subscribe to the store ``` store.subscribe(self) { $0.select { $0 }.skipRepeats({ (old, new) -> Bool in return old.activeProject == new.activeProject }) } ``` If my `AppState` is `Equatable`...