• morphballganon@lemmy.world
    link
    fedilink
    arrow-up
    1
    arrow-down
    15
    ·
    9 months ago

    One of my big takeaways from CS classes was that goto loops are more efficient than for loops. So I’d start with comparing that with a recursive function.

    • xmunk@sh.itjust.works
      link
      fedilink
      arrow-up
      14
      ·
      9 months ago

      Gosh I hope to hell you’re being sarcastic because that’s one of the worst takeaways you could probably get.

      Technically, for performance, machine code has a higher performance ceiling than code produced by a compiler… but it’s so fucking likely that you’re going to make an error, either logically or in terms of performance, that machine compiled code almost always out performs hand written assembly written by gurus.

      In terms of goto vs. for… gotos make it extremely easy to accidentally leave or enter functions without pushing or popping the appropriate frames so it’s highly likely you’ll end up introducing a really hard to track down segfault… there are better excuses you can find to learn gdb.