> We're already using 'eq' to perform equality testing, and in the interests > of maintaining a consistent design I would choose to stick with something > eq-related as opposed to changing it to 'same'. > > eqaddr/eqval? eq_addr/eq_val? eq_address/eq_value?
Oops, correction there - I'd forgotten an earlier post that pointed out the proposed functionality of eqval/eq_val/eq_value had already been implemented.
