Closed spencewenski closed 2 weeks ago
This would be a breaking change
Do we want methods to also take an owned context/state? This could future proof the methods.
Do we want methods to also take an owned context/state? This could future proof the methods.
Not right now at least. I think this would potentially give the incorrect perception that the state could be modified. That won't work by default unless the consumer implements an internal-mutability pattern.
It may be useful for consumers to be able to put state on their App implementation that they can use in the app trait.
This could also be a transition step towards a builder-style approach to building the app, where we provide a default app impl, but still allow consumers to directly use the trait impl if they want.