This will be very helpful. I was wondering; just like we disabled quite some warnings on mac/clang right now, maybe we should disable the massive amount of unused-parameter warnings for now, get this PR merged, and then offer someone a box of chocolates to handle the unused parameters?

I disabled the unused parameter warnings when using STORM_WARNING_AS_ERROR. The CI moves a bit further now and I can take a look at some of the other warnings in due time.

How can I handle this warning? It is a custom warning so I am not sure how to ignore it. I tried using the CMake flag STORM_WARNING_AS_ERROR but I would also need to export it into the config which seems a bit overhead for one warning.

How about CMake's add_compile_definitions( ... )

Needs #765

Most of the warnings should be fixed now. There are still at least three types of warnings open, but I am currently not knowledgeable enough to fix them. If you know how to address them, feel free to let me know.

All warnings should be fixed now. Thanks to @sjunges for some pointers on how to fix them.

There are even more warnings if we enable STORM_ALLWARNINGS but this is a separate task for another time.

We opted to first merge the fixes to warnings in the source code, see #792. Afterwards, we can address the remaining CMake questions here.