replace BitAndAssign example with something more evocative

[matthew-piziak]

This is the augmented-assignment version of PR #35809.

r? @GuillaumeGomez

[GuillaumeGomez]

Like discussed on IRC, please write simpler examples.

[matthew-piziak]

Copy-pasting the IRC discussion here. I'd link to the logs, but I can't prevent them from truncating prematurely.

https://gist.github.com/matthew-piziak/a2dd18e897eb3d4113459a945d85296b

[ollie27]

I like this example, however it's not clear what should happen if the Vecs are not the same length. I think the easiest thing to do is use an array instead. Doing that and simplifying the implementation gives something like the following:

use std::ops::BitAndAssign;#[derive(Debug,PartialEq)]structBooleanVector{value:[bool;4],}implBitAndAssignforBooleanVector{fnbitand_assign(&mutself,rhs:Self){for(x, y)inself.value.iter_mut().zip(&rhs.value){*x &= *y;}}}fnmain(){letmut bv = BooleanVector{value:[true,true,false,false]};
bv &= BooleanVector{value:[true,false,true,false]};let expected = BooleanVector{value:[true,false,false,false]};assert_eq!(bv, expected);}

[matthew-piziak]

I've taken the improvements in #35993 and applied them to this PR. I figured that a simple assert_eq! was cleaner than enforcing a particular length in the struct, but let me know what you think.

[matthew-piziak]

@bors retry

[GuillaumeGomez]

Thanks!

@bors: r+ rollup

[bors]

📌 Commit ba69bc8 has been approved by GuillaumeGomez