• @Perroboc
    link
    571 year ago

    int unused_variable = 0;

    Dude wtf is your problem don’t just leave things lying about there don’t you know how to code I mean what the- I don’t go to your house and leave shit on the floor and just—

    int _unused_variable = 0;

    Ok. We cool.

    • @[email protected]
      link
      fedilink
      110 months ago

      sometimes you need an unused variable. some uses in rust:

      // destructuring
      let (width, _height) = get_dimensions();
      
      // trait implementations (i couldnt think of a better example for this)
      impl Into for AlwaysZero {
          fn into(_value: Self) -> {
              return 0;
          }
      }
      
      // some types (eg. Result) must be 'used'
      // assigned to a variable if we dont care about the return value
      let _ = returns_result("foo");
      
  • @[email protected]
    link
    fedilink
    English
    481 year ago

    mfw my face when the go compiler fucking screams at me because I dared to declare a variable and not use it

    • @[email protected]
      link
      fedilink
      English
      231 year ago

      IF THIS IS INTENTIONAL PUT AN UNDERSCORE BEFORE THE VARIABLE NAME YOU ABSOLUTE FUCKING MORON

    • @clearleaf
      link
      101 year ago

      “Don’t worry too much about your loops bro, I am the apex of computer science research, I know every optimization in the book.” Ok want to compile this? “Is that… An unused variable?!? WHAT THE FUCK ARE WE GOING TO DO GOD IS DEAD”

      • @[email protected]
        link
        fedilink
        English
        21 year ago

        honestly my dumb ass will choose for i in list: over for i := range slice { every single time. I’m ugly and I’m proud!

  • Bappity
    link
    English
    29
    edit-2
    1 year ago

    I am guilty of passing Exception variables into try catches and not using them

  • Limitless_screaming
    link
    fedilink
    131 year ago

    Function is changing a global variable, the global variable is checked after every call to the function. That’s your return value.

    • qazOP
      link
      12
      edit-2
      1 year ago

      I spent 3 hours debugging the serialization code to find out it the crash was because the function didn’t have a return statement.

  • @gredo
    link
    91 year ago

    laughs in golang

    • qazOP
      link
      81 year ago

      I would love to use golang for this but it’s standard library alone is bigger than the amount of available RAM.

      • @gredo
        link
        21 year ago

        Interesting, since golang only includes the parts of the stdlib that are used in the executable binary.

        • qazOP
          link
          41 year ago

          I just tested it and a simple hello world program still produces a 1.7MiB binary, while the device only has 512KiB of RAM.

          package main
          
          import "fmt"
          
          func main() {
              fmt.Println("hello world")
          }
          
          • @[email protected]
            link
            fedilink
            31 year ago

            Strip the debug info, should be a lot smaller. Also check out TinyGo, it’s meant for embedded devices

      • @gredo
        link
        11 year ago

        BTW: what are you using instead to get small binaries/scripts?

        • qazOP
          link
          31 year ago

          I’m currently using C++

          • @mkwt
            link
            21 year ago

            Likely your C++ implementation also doesn’t ship the full standard library. And you may even turn off exceptions and RTTI.

  • @[email protected]
    link
    fedilink
    11 year ago

    Idk, mb they expected you to modify smth passed by reference/pointer, and the compiler’s too busy to care :)

  • @marcos
    link
    -21 year ago

    Ok, you are certainly in one of those languages where plenty of your functions shouldn’t return a value, and you won’t ever let the compiler know that.

    On all of the other languages, it’s an error, not even a warning.

    • qazOP
      link
      91 year ago

      It’s C++ and it just causes a SIGILL.