Memory Leak?

[devxoul]

Memory Leak?

[devxoul]

@reejosamuel, RxTodo is the most up-to-date code. Drrrible and Cleverbot will be updated soon :)

It's true that more enum cases can cause more complexity. But it has same complexity compare to the current architecture (Observables per each input/output). The most benefit of using enums is that compiler can validate unused/misused cases.

[reejosamuel]

I tried the new action-state architecture you proposed. in the todo app i don't see any leaks at all when I open and close next view controllers. But in the dribbble one with the new architecture i still see some mismatch.

With the new architecture one thing I noticed is that the cyclometric complexity of a function can increase quite a bit in a larger application because of using so many switch cases. I was thinking how we could improve so many switch cases in the mutate and transform methods but overall it seems like much more single responsibility, easier to read and functional than earlier.

[devxoul]

Not sure but there might be memory leaks. I'm currently working on a new code base(#19) which doesn't have memory leaks at all :)

[seivan]

@reejosamuel Nothing prevents you from breaking down your reducer into smaller reducers.
Your enum can contain other actions. I think that's how Elm-lang does it and Redux has its combineReducer()