storm
storm copied to clipboard
Print proper reason when a property can not be handled
The canHandle methods of the model checkers should report some kind of indication why the property is not supported (e.g., because the model has multiple initial states, ...).
Right now, the verifyWith*Engine
API methods just return a nullptr if canHandle is false. This is not helpful for the user and can lead to confusion (e.g. here)