21 Apr
2020
21 Apr
'20
10:22 p.m.
Have you written your own version that does this check for input iterable equality?
No, unfortunately. As I've mentioned before, it just feels too heavy to wrap all of these nice builtin zip objects to check things that "must" be true. If this option were available, I would certainly enable it in the places I didn't care enough to be defensive before. Maybe this is an argument against adding the functionality, but I see it as an argument for. We already perform most of the logic for this check internally, so why force users to make a (possibly buggy) wrapper that effectively does the same thing?