- Parameters are currently assumed to be from a safe source (works for many use-cases, but yes, it is something to be wary of).
- The eval access is supposedly more efficient (as polymer guys claim, but I'm not aware of a benchmark)
- Unlike the 'nester' lib and many others, this key-path lib is designed to separate the path input processing (mainly parsing) from object access. This allows for caching/memoizing and for treating the paths as comparable objects (e.g., checking if 'prop[3]'==='prop["3"]').