Can/should we remove the `--warnings-as-errors` option?
Currently some things in Pleroma use the
--warnings-as-errors option. Typically warnings aren't really a problem for building and running software. By using this option Pleroma instances can (and have) brake just by updating Erlang/Elixir. What's even worse is that it will only fail once the instance restarts, so there is even a change that people don't know that it was an upgrade that caused the issue.
(At least that is how I understand it seeing
Compilation failed due to warnings while using the --warnings-as-errors option.)
It seems to me that this makes Pleroma more fragile. Pleroma is partly aimed for easy self-hosting. Having your instance fail like this means
- more stress during upgrades/restarts,
- more work for the self-hoster in question and
- Having to start troubleshooting/upgrading when you maybe didn't have much time for (which only adds stress and discomfort)
This makes me wonder; Can we reconsider and remove this
--warnings-as-errors option? (And is there a specific reason why this option is used atm?)