| ▲ | Charon77 a day ago |
| Absolutely love how readable the entire project is |
|
| ▲ | koakuma-chan a day ago | parent | next [-] |
| It's AI generated |
| |
| ▲ | Revisional_Sin a day ago | parent | next [-] | | How do you know? The over-commenting? | | |
| ▲ | koakuma-chan a day ago | parent | next [-] | | I know because this is how an AI generated project looks. Clearly AI generated README, "clean" code, the way files are named, etc. | | |
| ▲ | magackame a day ago | parent | next [-] | | 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. | |
| ▲ | cmrdporcupine a day ago | parent | prev [-] | | 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. | | |
| ▲ | koakuma-chan a day ago | parent [-] | | 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. |
|
| |
| ▲ | adastra22 a day ago | parent | prev | next [-] | | Because the author said so on Reddit. | |
| ▲ | GardenLetter27 a day ago | parent | prev [-] | | The repeated Impls are strange. | | |
| |
| ▲ | a day ago | parent | prev [-] | | [deleted] |
|
|
| ▲ | emporas a day ago | parent | prev | next [-] |
| 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. |
| |
|
| ▲ | yieldcrv a day ago | parent | prev [-] |
| 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. |
| |
| ▲ | GardenLetter27 a day ago | parent | next [-] | | 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. | | |
| ▲ | cmrdporcupine a day ago | parent [-] | | 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. |
| |
| ▲ | jmaker a day ago | parent | prev [-] | | Not sure what you’re alluding to but that’s just ordinary Rust without performance or async IO concerns. |
|
