Most fullmatch() and pairmatch() methods call match_on() on their first arguments, in the process consulting any caliper= arguments (or within= arguments, ...) that were given to the full()/pair() call. But neither fullmatch.matrix() nor pairmatch.matrix() does this, with the result that caliper= arguments are silently ignored. Confusing and likely to induce errors.
We currently address this issue as it pertains to within= arguments -- in the case of fullmatch(), here -- and we might do something similar for caliper. (It will require a tad more effort, however, because any caliper= specifications would be hiding in the ....)
Most
fullmatch()andpairmatch()methods callmatch_on()on their first arguments, in the process consulting anycaliper=arguments (orwithin=arguments, ...) that were given to thefull()/pair()call. But neitherfullmatch.matrix()norpairmatch.matrix()does this, with the result thatcaliper=arguments are silently ignored. Confusing and likely to induce errors.We currently address this issue as it pertains to
within=arguments -- in the case offullmatch(), here -- and we might do something similar forcaliper. (It will require a tad more effort, however, because anycaliper=specifications would be hiding in the....)