News for hackers. Stuff that matters.
Re:What Makes Code Hard to Read: Visual Patterns of Complexi... by aquariusDue on Wednesday March 12, 2025 @07:27AM (#43342091)
Here's an abomination of my own design in Rust for example:

   for (index, node) in nodes
       .expect("Error: No blocks for the Body")
       .children()
       .expect("Error: blocks node has no children")
       .nodes()
       .iter()
       .enumerate()
   {
       let block = Block::new(node, index);

       self.blocks.push(block);
   }
Re:What Makes Code Hard to Read: Visual Patterns of Complexi... by maleldil on Wednesday March 12, 2025 @03:32PM (#43346845)
Why the for loop instead of mapping the enumerate iterator into Block::new and collect::Vec?
Re:What Makes Code Hard to Read: Visual Patterns of Complexi... by aquariusDue on Thursday March 13, 2025 @05:33AM (#43351625)
I lack a good answer other than it didn't occur to me, now I have some code to refactor. Thanks!
Re:What Makes Code Hard to Read: Visual Patterns of Complexi... by maleldil on Thursday March 13, 2025 @11:37AM (#43354393)
FWIW, I've had to write similar code when there's some complex "folding" operation. I use map/filter a lot, but fold/reduce/accumulate always seemed harder to understand than a for loop. I also prefer nested loops rather than nested iterators.