Helehex

another thing about `repr`, it takes non-printable characters and gives the representation of them, such as `\n`. I already did this in one of my side projects, so I can...

Yeah that might be good. I'm not even sure this is something that would get pulled because of that, but figured i'd give it a shot since it's just a...

sora pointed out that this would not be confluent under generalization, and we agreed that for now, `SIMD.__bool__()` should be constrained to size=1, so that if the logic of `bool(a...

we also agree that being explicit about `reduce_and`/`reduce_or` makes the most sense. maybe something like specifying parameters on self would be nice here, to see the error in the editor:...

ok this feel like the right way to go - Added some simd helper functions: `_all_equal`, `_any_equal`, `_all_not_equal`, `_any_not_equal`. - Changed every case i could find of implicit reduce functions...

I'm still not sure this should or will get pulled. It feels good writing simd code like this. You get a compiler error when converting a `SIMD` with size >...

another trade-off that should be mentioned: Ideally, everything should be boolable, and this breaks that but like sora mentioned, when working with simd size > 1, the boolability causes trouble

everyone i've talked to likes how `simd.eq` returns a simd though

I agree we need a proper proposal though. For now i'll just open a separate pr for constraining `simd.__bool__`. That will also align better with `simd.__int__`

removing the bool constructor wasn't necessary, but it helped weed out all the cases of implicit reduce and is also very much related