Obsolete function?

How hard can it be to place a breakpoint inside (or even just a log statement) and watch when it's hit?

@kamen are you trying to apply logic to a shitty meme?

@Kimmax If this is really taken from a piece of code, then it's not just a meme.

@molaram Now imagine that there is something like JavaScript's eval() that can call functions dynamically (so that you wouldn't be able to find it).

@molaram I'm not saying it's good practice, I'm saying it's possible.

@molaram No, there are a lot of frameworks that do all sorts of "magic", where something abstracted 3 or 4 levels deep will call a method based on the name of something else based on something dynamically set, or the existence of a file, or an environment variable. *cough cough rails devs*

Doing a full grep for the function name, its permutations, etc is not going to turn up anything.

@madumlao +1 I remember that calling a function with a callback function which itself took either 3 or 4 arguments yielded different results.
Wrapper((a, b) => a+b) and
Wrapper((a, b, _unused) => a+b)
Will make a difference...

My linter warned me about ‘_unused’ being unused and I removed it. Then program crashed.

My comment was:
“Do not fucking remove that unused parameter. It will make the program crash!”

You guys, guess the language (and the library making use of that phenomena)!

A fragile equilibrium of bugs and memory leaks somehow canceling each other out keeps this masterpiece alive

@uyouthe @uyouthe Isn’t that the essence of a program?