Is the (pseudo?) code there for state mutation representative of a widely used pattern? It looks like using a pattern from a functional programming book, but applied to mutable data. What I mean is this snippet: function handleAddTodo(state) { if (!newTodoField) { state.error = 'Empty field!' } state.todos.push(state.newTodoField) state.newTodoField = nil return state; } This looks like a function newState = fun(oldS…
This is not an unfortunate example. With the absence of persistent data structures it is inefficient or difficult to write the state transition functions as pure functions.