• 8
    Load bearing stairs.
  • 2
    I guess there's a "Fire exit" sign on the inside of that wall.
  • 6
    Parkour shortcut.
  • 2
    its for the superheroes
  • 3
    @metamourge loadstairing
  • 0
  • 1
    It is stairs for Balconies
  • 1
    i never understood this. is it really so hard to remove code paths that are unused? If nothing's using it it shouldn't crash if it disappears, no?

    Or is your language's parser/compiler+linker/interpreter just shit? Is the rest of the code relying on things it shouldn't? I don't at all understand. It's not even that hard when you're working with machine code unless deliberately made to be an asshole if anything changes...
  • 4
    @Parzi: Bad computer programmers can do some amazing things.
  • 0
  • 1

    Well, if you remove a function which has zero measurable side effects and does not return any value (void), but it is being called, it would crash the program if you removed the function.

    In interpreted languages you'd pretty much always end up severely wounded when taking wrongly placed or nonexistent stairs during runtime.

    But even in compiled languages with a high degree of type system safety you could end up with issues.

    In Rust, maybe_stairs.unwrap().climb() would "completely according to expectations" just terminate the program if you are attempting to climb something that "either IS or IS NOT a flight of stairs", and turns out to NOT be a flight of stairs.

    Technically not a runtime error, because you are literally programming it to "climb stairs if they exist or exit program" -- intended behavior.

    But it solves the problem of stepping on a nonexistent flight of stairs by shutting down the universe for safety, which might be considered extreme.
  • 0
    It's just commented out so the wall interpreter won't try to execute it.
Add Comment