@snoopi returns timing data in (t, mi) tuples; some of the new @snoopi_deep framework uses a pair t => obj instead. We should be consistent. I confess to having one concern with pr = t => obj: pairs are often used in contexts where pr.first is a "key" and pr.second is a "value." There is no sense in which t is a key for anything. The names .first and .second are neutral, so from that perspective this is not an abuse, but the printing t => obj reinforces the key/value association.
@snoopireturns timing data in(t, mi)tuples; some of the new@snoopi_deepframework uses a pairt => objinstead. We should be consistent. I confess to having one concern withpr = t => obj: pairs are often used in contexts wherepr.firstis a "key" andpr.secondis a "value." There is no sense in whichtis a key for anything. The names.firstand.secondare neutral, so from that perspective this is not an abuse, but the printingt => objreinforces the key/value association.