Question about MaterialDialogState #178
Description
Not really an issue, but I couldn't find other ways to ask the question.
I was learning about creating custom State objects, so I thought to give a look into how MaterialDialogState was implemented in this library to have a real (and simple) use case to analyze, but I noticed that in the Saver the library uses a wildcard for the Saveable type parameter, and by looking at how the class is structured I was expecting a Boolean instead. Could anyone explain to me what's the reasoning behind the wildcard type parameter choice?