Description
I definitely do like polymorph.access:at more than access:access in large part due to the minimal overhead of the former.
I'm not sure how others are using at. I've been using it as a replacement for the traditional gethash, aref, nth when I don't want to think about the class of the container especially during the initial prototyping phase. This also means that I am expecting it to be used in code that handles the nil nil returned by gethash when the key does not exist. However, when the key does not exist, at signals an error, and it is at-safe that returns nil nil. So, I'm required to use at-safe rather than at which feels a bit verbose.
Are there any opinions on keeping things as they are? Or, if it is okay to switch the two, I can issue a PR that replaces at with at-safe and vice-versa.