Should state be kept separate from callbacks in the returned result?

Currently we return an object from useMethods which is a mixture of state and callbacks:

const initial = { count: 0 };

const methods = state => ({
  increment() {
    state.count++;
  },
  decrement() {
    state.count--;
  },
});

// ...

const { count, increment, decrement } = useMethods(initial, methods);

but maybe they should be kept separate, a la useState and useReducer:

const [{ count }, { increment, decrement }] = useMethods(initial, methods);

One advantage of this would be the option to use primitives instead of objects for state. For example in this case we could use a simple number for the state:

const initial = 0;

const methods = count => ({
  increment: () => count + 1,
  decrement: () => count - 1,
});

// ...

const [count, { increment, decrement }] = useMethods(initial, methods);

[Noitidart]

Thank you! Super awesome!

[pelotom]

@Noitidart yes, except that I’ve also reversed the argument order (#3) to be consistent with that of useReducer, so:

const [count, { increment, decrement }] = useMethods(methods, initial);