• nexussapphire@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    Last day at the company, pushed over 5,000 commits. Just style changes, still passes all the checks.

    • subignition@fedia.io
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      High chance that it’s a Python programmer who is really unhappy about having to work in Java, lol

      • _stranger_@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        3 months ago

        Heh, so in Python it’s possible to overload operators in the context of objects. I bet it would be possible to overload tabs to do the same thing as colons inside a context manager, but that’s pure speculation.

        • takeda@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          3 months ago

          Perhaps I don’t understand you, but I don’t think there’s a way to override spaces in python in any way. The spaces are handled by the parser.

          • _stranger_@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            edit-2
            3 months ago

            You can define what happens for an object when an operator is applied (like +, /, or -) so that you can obj+obj. I wonder if there’s a way to override “tab” such that it acts like a “:”, but from inside the language (this is trivial if you edit the language itself like you suggest). Thinking about it more, I’m guessing not since “:” isn’t an operator and this doesn’t have a corresponding __operator__ function.

            • palordrolap@kbin.run
              link
              fedilink
              arrow-up
              0
              ·
              3 months ago

              If Python has anything like Perl’s source code filters, then anything’s up for grabs, but Perl is kind of weird in a way that Python was specifically designed not to be. Or at least Python 1 was. Things may have changed in the intervening couple of decades.

              If it’s just plain overloading, then whitespace is probably off the table. Spaces, even required spaces, aren’t so much syntax as they are structure. You could argue that the curly braces of some other languages are more syntactic than Python’s whitespace, because it’s actually Python’s magic colon and the first unindented line (lack of whitespace!) that serve that specific syntactic purpose.

              Examples of Perl’s source code filters range from turning a program into binary representation of the syntax tree and still having it be executable, to new syntax, to writing programs entirely in Latin or something that looks almost but not entirely unlike it, anyway.

  • magic_lobster_party@kbin.run
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    I’m more concerned about that poor stack with all those recursions.

    It’s also O(n^2). I’m not sure what they’re trying to do, but I’m sure it can be done in O(n).

    Reject.

  • GissaMittJobb@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    Automatically enforced deterministic formatting is the best, there’s nothing that beats it. The productivity in just being able to format on save knowing that the code will be in the ideally formatted state, along with the anti-bikeshedding properties of this strategy, makes it unbeatable.

    • h0bbl3s@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      gofumpt and gofmt are the best. One of the reasons if I have a choice I’ll code in go. I heard rumblings that rust was working towards having rustfmt be a standard crate.

      • GissaMittJobb@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        3 months ago

        Go is in a good position, yeah. JavaScript has prettier, which is nice. Java has google-java-format. Python has ruff, which is quite good. Kotlin has ktfmt, which I believe made a mistake with their standards by not following the standard formatting guidelines for the language, but whatever. Uniform and deterministic for the win.

      • Username@feddit.org
        link
        fedilink
        arrow-up
        0
        ·
        3 months ago

        What do you mean? rustfmt is the de facto standard and is easily run using cargo fmt. Most projects use it along with clippy, the standard linter.

  • demizerone@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    Auto formatter as part of the expected language tooling is Go’s greatest move, even if their formatter doesn’t go far enough.

  • mox@lemmy.sdf.org
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    3 months ago

    Having grown up with C made me assume semicolons and braces were needed to avoid subtle errors, but experience with more recent languages showed me that it’s possible to reliably parse the same semantic cues that humans use: indentation, parentheses, and other such context. (Perhaps this was less viable when C was invented, due to more constrained hardware.)

    I was skeptical at first, but in practice, I have never encountered a bug caused by this approach in Python, Nim, or any other language implementing it consistently, over the course of a decade or two. Meanwhile, I have seen more than a few bugs caused by brace and semicolon mistakes.

    So nowadays (outside of niche domain-specific languages) I see braces and semicolons as little more than annoying noise and fuel for religious arguments.

    • Ephera@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      Well, Python kind of does the reverse of a semicolon: If you want to continue a statement over multiple lines, then you have to \
      escape it.
      Python also then tries to avoid multi-line statements for that reason, but yeah, in most other languages this would be equally as annoying as semicolons are.

      There are some languages which use neither, for example Scala, but I can at least say that while I consider the people behind Scala and Rust equally competent and the languages more or less equally modern, Rust just completely blew it out of the water in terms of error messages despite being much younger. (Not because Scala is bad, Rust is just incredibly good there.)

      And yeah, I’m suspecting that Rust using semicolons makes the difference there.
      While Scala will pretty much have to guess where a statement with compile error ends, Rust just knows it ends at most at the next semicolon.

      I will also say my experience is opposite of yours. I have managed multiple times to try to access a variable in Python, which wasn’t in scope anymore, because the indentation wasn’t enough of a visual cue to me.
      And in any modern language, missing/missplaced semicolons or braces are a compile error, with clear error message where it’s missing. I genuinely don’t even know how you’d get a bug out of that.

      • sparkle@lemm.ee
        link
        fedilink
        Cymraeg
        arrow-up
        0
        ·
        edit-2
        3 months ago

        I am a Scala and Rust fan. I can corroborate what you said

        The part about no semicolons/curly braces I like in Scala is that I can write a function and it’ll look virtually indistinguishable from a regular ol variable. Functions become much less of a ritual and integrate more nicely with the rest of the code. Other than that though, Rust definitely wins out because of the curly braces & semicolons. I use curly braces in most situations in Scala where I’d normally use them in Rust, and I would use semicolons everywhere in Scala if it weren’t considered unidiomatic. Whitespace-significant syntax is just really annoying to deal with. Using Python or even maybe F# makes me want to die because I keep accidentally missing an indent somewhere or indenting too much somewhere else or using the wrong kind of whitespace and the entire program implodes. At least Scala and Kotlin keep it sane

        Also it’s just way harder to visually organize in whitespace based languages. You basically have to do a bunch of magic tricks to make the code look slightly different in a specific scenario than what the language wants you to. Rust allows you to actually visually organize your code easily while also having a strong style rules which you shouldn’t stray too far from (or else the compiler will yell at you).

      • mox@lemmy.sdf.org
        link
        fedilink
        arrow-up
        0
        ·
        3 months ago

        Well, Python kind of does the reverse of a semicolon: If you want to continue a statement over multiple lines, then you have to \ escape it.

        That’s not true. Being within parentheses, brackets, quotes, etc. is enough for the parser to know you’re continuing. In practice, I find that context is already present in most cases.

        For the other cases, occasionally surrounding an expression in parentheses is easy enough. Long conditionals probably deserve parentheses anyway, for clarity.

        • Ephera@lemmy.ml
          link
          fedilink
          arrow-up
          0
          ·
          3 months ago

          Well, it mostly being already correct is what I meant with Python avoiding multi-line statements.

          In JVM languages, Rust etc., it’s for example popular to use Fluent Interfaces. These also reduce visual clutter and the number of variables in scope (and/or the need for mutability).

          I did not know about enclosing them with parenthesis, but apparently that works, too, as this library shows: https://pypi.org/project/fluentpy/

    • leftzero@lemmynsfw.com
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      As someone used to working in c# (and before that Java, C++, Visual Basic, and Pascal) I haven’t seen any brace or semicolon related errors since the days of Borland IDEs (any remotely self respecting IDE will highlight them and refuse to compile, these days), but working with Kotlin has shown me that I, at least, read code with semicolons slightly faster than code without.

      There’s a reason we use punctuation when writing, and the same applies to code.

      • ChickenLadyLovesLife@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 months ago

        Borland IDEs

        Ugh, you just gave me Turbo Basic flashbacks. My favorite thing was that variable names could be as long as you liked and mixed case, but the compiler only used the first two letters and case insensitive at that. So “BatShitCrazy” and “BALLPARKESTIMATE” actually referenced the same variable.

      • mox@lemmy.sdf.org
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        3 months ago

        Haha… Yes, I’ve found yaml to be problematic in this area, too. Probably because it lacks the context cues and modularity of a programming language.

    • GBU_28@lemm.ee
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      3 months ago

      Plus any decent editor catches when lines are unreachable or in violation due to misformatting.

      If not that, which seems unlikely, your unit tests would

      • mkwt@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        3 months ago

        When Fortran was created, each line was a separate punched card. The syntax made sense for that medium.

        C was setup from the start for use on teletypes with fancy line editors like ed.

    • magic_lobster_party@kbin.run
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      In Java it’s quite difficult to forget semicolon and still have a syntactically correct program.

      I think braces are incredibly important. With Python it can be confusing which indentation is correct when copying code between files. Different indentations can easily be still syntactically correct, but the outcome is vastly different. It’s often I have to double and triple check to verify I copied the code with correct indentation.

      • mox@lemmy.sdf.org
        link
        fedilink
        arrow-up
        0
        ·
        3 months ago

        It’s often I have to double and triple check to verify I copied the code with correct indentation.

        I vaguely remember facing that issue once or twice in the past, but certainly not often. It was because the pasted code was too long for its starting point to be easily found in my editor, even if I scrolled up or down a bit.

        If this happens to you often, I wonder: perhaps the code you maintain should be broken into smaller functions anyway? If I was in that situation again, I think I would simply place a bookmark before pasting and then jump back to the bookmark to indent/dedent the pasted block appropriately.

    • Caveman@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      Who’s going to write the extension so that they are all hidden and automatically inserted?

    • VonReposti@feddit.dk
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      3 months ago

      I think you’ll like Ruby. It has mostly done away with braces and code blocks end with end, e.g.

      def create
        unless admin redirect_to new_session_path and return
        
        @product = Product.new product_params
      
        if @product.save
          flash[:success] = "New product has been created!"
          redirect_to edit_product_path(@product) and return
        else
          flash[:error] = "Something went wrong!
          render :new
        end
      end
      

      This is working code that I simplified a bit from an old project of mine.

      • Caveman@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        3 months ago

        Ruby syntax is nice although I prefer python way of enforcing indentation instead of adding "end"s. Personally I just want a statically typed language with enforced indent as syntax.

        • VonReposti@feddit.dk
          link
          fedilink
          arrow-up
          0
          ·
          3 months ago

          Funny, the forced indentation is what I hate about Python. If you think a missing semicolon can be hard to catch, don’t ever think about a missing whitespace :p

          The end keyword really isn’t a big deal for me. I find it to be a good way to easily spot the end of a method. But if you wouldn’t like it I’d still find it a good compromise to avoid syntax issues due to whitespace.

          • hglman@lemmy.ml
            link
            fedilink
            English
            arrow-up
            0
            ·
            3 months ago

            i can count on one hand how many times ive had white space issues in 15 years of using python. its just not an issue

            • 0ops@lemm.ee
              link
              fedilink
              arrow-up
              0
              ·
              3 months ago

              Same and agreed, especially if you keep your functions small and focused as you should. 3-5 indents is nbd to keep track of, and if you need more than that… No you don’t, refactor.

              I’ve had way more hangups with brackets then indentation, personally, not that either is a super frequent issue, but I’m indenting anyway, so brackets are redundant and just another thing I have to keep track of

      • barsoap@lemm.ee
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        3 months ago

        That’s just Algol instead of B. Most languages use the one or the other, then there’s sexpr-based languages (lisp, scheme), lua (technically Algol but not needing semicolons while also not needing newlines so it’s definitely special), and layout syntax (Haskell, or, if you want a bad implementation, python).

    • bss03@infosec.pub
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      Might check out the Haskell layout rules.

      Basically, when you leave out the ‘{’ then Haskell uses your intendation to insert ‘;}’ on later lines between the leading whitespace and the first token.

      There some really old Haskell code out there that lines up the ‘{;}’ characters on the left under block-introduction keywords.

      • barsoap@lemm.ee
        link
        fedilink
        arrow-up
        0
        ·
        3 months ago

        It’s not just old Haskell code that’s how you write Haskell if you want explicit braces. Well, mostly generate, but it’s still the idiomatic formatting (and when you generate you always generate braces because it’s easy to get layout subtly wrong when generating).

        Haskell also does the whole

        data Foo = Bar
                 | Baz
                 | Quux
        
        foo = [ Bar
              , Baz
              , Quux
              ]
        

        thing, makes sense to apply it to braces especially as they’re seen only very rarely. Single-line, yes, but not multi-line.