• spongebue@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      1 day ago

      I have no idea why you’d need that especially since return y() is pretty easy, but… I want it!

      (Actually, I guess a super simple way of overloading a method, like fun x() = x(defaultValue) could be neat)

      • calcopiritus@lemmy.world
        link
        fedilink
        arrow-up
        8
        ·
        1 day ago

        This can also be a side product for code blocks being expressions instead of statements.

        In rust for example they are, so it’s not rare to see functions like:

        fn add_one(x: i32) -> i32 {
            x+1
        }
        

        This lets you do amazing things like:

        let x = if y < 0.0 {
            0.0
        } else {
            y
        }
        

        which is the same as x = y < 0.0 ? 0.0 : y

        But is much better for more complex logic. So you can forget about chaining 3-4 ternary operations in a single line.

        • SlurpingPus@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          12 hours ago

          Lisp programmers seeing these ‘amazing things’:

          But yeah, every time I’m trying to do a ternary in Lua, I miss being able to just throw in an if. Thankfully it can be amended with Fennel.

      • Eager Eagle@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        23 hours ago

        default values is one of my pet-peeves after using Python regularly. I wish more languages would let you just do something like def do_thing(arg=default_value) without hoops like builder pattern, function overloading, or whatnot

        • SlurpingPus@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          15 hours ago

          I mean, the go-to approach in Lisp, for example, is to have null as the default value (which doubles for false in there). And check for that in the function.

            • SlurpingPus@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              14 hours ago

              In Lisp, at least the Emacs Lisp with which I have experience, it’s customary to put in nil (Lisp’s null) for any omitted arguments in the middle that you can’t be arsed to specify — aside from just leaving off arguments at the end. In JS, typing in undefined in every such case would probably be an annoyance, so I’m guessing coders need to check for both undefined and null in these circumstances.

              Overall, it’s remarkable how Lisp teaches one to be much more relaxed about programming practices than is typical for mainstream languages. Design patterns? Data structures? Shit, just pass in a list or an assoc array, and maybe a function here and there. Also everything is an expression, enjoy your ternary (if) at any point anywhere.