4 ms·

So many silly workarounds being suggested here. You should be able to pass a flag to accomplish this, anything else is simply annoying and drives away new users

• loopz 7y ago
  That's a feature! You could have a flag, but we all know this is going to be abused. Seems devs have opted away from such, though it is understandably opinionated and require some thought.
  • kstenerud 7y ago
    In what way would it be abused? "To use this library, you must enable warnings in your build"? Yeah, that's gonna fly. If your code won't compile with default options, nobody will want to use it. This is just a solution in search of a problem.
    • loopz 7y ago
      Isn't such types of shenanigans SOP in many communities? Not against options per se, but can see the arguments against implicitly hiding alternative behaviour. Many compilers fail to be simple, performant and provide the right incentives. Again, never had problems adding experimental code (// TODO: Remove), bootstrap-code, extra debug-info, etc. Ie. Why you should want to prefer refactoring.
  • bschwindHN 7y ago
    It's not a feature, it's an annoyance. Don't use the flag in CI and don't allow merges until CI passes. It's not hard.