On 2015-07-15 6:47 PM, Jeff Gilbert wrote:
"Arg warts improve backtracking for debugging" Regardless of the validity of "Arg warts help illustrate information flow", the use-case of backtracking to 'origin' of aFoo is also unconvincing, since you'd only need to go back once more than previously before moving once back 'up'. Either way sounds eminently automateable. -> No practical change, thus irrelevant.
I don't understand what you're saying here at all. It seems that you're saying that this use case is not interesting to you, and that's OK, but that doesn't make it irrelevant. :-)
"It's hard to implement" This is irrelevant for new code, and bulk-change is feasible once we have -Wshadow. (which isn't too hard. We shouldn't have shadowing in our code anyway, so we want -Wshadow regardless of this discussion) Besides, a number of our internal projects and modules already don't have it, so it's free for them. -> Non-trivial, but not too hard to implement.
The "isn't too hard" part of the above is factually incorrect. See bug 563195 for why.
So, when you say "I like aFoo because it lets me know which vars are args", is there any un-touched-on aspect of the information "this var is an argument" that is useful to know? How does every other project survive without it?
Given Benjamin's response, there is really no point in arguing over this any more, but just as a thought exercise: is there anything that would convince you that this is useful for some people? I would expect having those people tell you that it's useful for them should be a good enough reason to assume that it is!
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
