koakuma-chan 18 hours ago

It's AI generated

Reply View 10 replies
  • Revisional_Sin 18 hours ago

    How do you know? The over-commenting?

    Reply View 8 replies
    • koakuma-chan 18 hours ago

      I know because this is how an AI generated project looks. Clearly AI generated README, "clean" code, the way files are named, etc.

      Reply View 3 replies
      • magackame 18 hours ago

        Not sure myself. Commit messages look pretty human. But the emojis in readme and comments like "// Re-export key structs for easier access", "# Add any test-specific dependencies here if needed" are sus indeed.

        Reply View 0 replies
      • cmrdporcupine 18 hours ago

        To me it looks like LLM generated README, but not necessarily the source (or at least not all of it).

        Or there's been a cleaning pass done over it.

        Reply View 1 reply
        • koakuma-chan 18 hours ago

          I think pretty clearly the source is also at least partially generated. None the less, just a README like that already sends a strong signal to stop looking and not trust anything written there.

          Reply View 0 replies
    • adastra22 14 hours ago

      Because the author said so on Reddit.

      Reply View 0 replies
  • [removed] 18 hours ago
    [deleted]
    Reply View 0 replies
emporas 19 hours ago

It is very procedural/object oriented. This is not considered good Rust practice. Iterators make it more functional, which is better, more succinct that is, and enums more algebraic. But it's totally fine for a thought experiment.

Reply View 1 reply
  • [removed] 12 hours ago
    [deleted]
    Reply View 0 replies
yieldcrv 19 hours ago

Never knew Rust could be that readable. Makes me think other Rust engineers are stuck in a masochistic ego driven contest, which would explain everything else I've encountered about the Rust community and recruiting on that side.

Reply View 3 replies
  • GardenLetter27 18 hours ago

    Most Rust code looks like this - only generic library code goes crazy with all the generics and lifetimes, due to the need to avoid unnecessary mallocs and also provide a flexible API to users.

    But most people aren't writing libraries.

    Reply View 1 reply
    • cmrdporcupine 14 hours ago

      Don't underestimate what some programmers trying to prove their cleverness (or just trying to have fun) can do if left unchecked. I think most Rust code does indeed look like this but I've seen plenty of projects that go crazy with lifetimes and generics juggling where they don't have to.

      Reply View 0 replies
  • jmaker 19 hours ago

    Not sure what you’re alluding to but that’s just ordinary Rust without performance or async IO concerns.

    Reply View 0 replies