3 ms·

This actually has nothing to do with how often the code is executed. Code is ranked by its referents.

• toxik 4y ago
  Right, which is exactly what I pointed out. The true call graph can only be obtained by basically running the program. Counting references is clearly a compromise here. To see its drawbacks, consider indirection and dynamism.
  • naniwaduni 4y ago
    This reaction is kind of like reading about a pre-election poll where the participants were selected by pulling them off 86th street at 11 am, and objecting that the percentages shouldn't be presented with more than two sig figs with a sample size of 100. You're not, strictly speaking, wrong. But the methodology is already known to be deeply compromised, so your objection is kind of out there.
    • toxik 4y ago
      It was an observation that the choice to use references is actually a must, because of the halting problem, which I found interesting. Not everything is an argumentation.
  • enneff 4y ago
    But this is about ranking code based on how central it is, for the purposes of choosing what to translate to TypeScript first. It’s not a compromise, it’s the correct approach. How often a line of code is executed is not relevant for this purpose.