Summary: I found it very confusing that running infer with --debug makes the report to be different. Intuitively, I expect (and I think majority of users would expect) that `--debug` makes things more verbose (and potentially more slow / consuming more memory and disk space), but does not change anything apart from it. One pro of preserving existing behavior, pointed by jvillard: - Suppose some check is experimental or disabled in the config. The users expect the issue to be found, but it does not show up. They run `infer --debug` to understand the behavior, and suddenly the issue shows up. I, hovewer, find this pro not important enough and potentially confusing the users even more. (If they want to investigate seriously, they can always use --no-filtering, and there are a lot of cases when the issue does not show up for others, much hard to undertand reasons, than the fact that it is disabled). Reviewed By: jvillard Differential Revision: D17113750 fbshipit-source-id: 46cc93503master
parent
d864fb2c89
commit
753580095e
Loading…
Reference in new issue