This repository was archived by the owner on Aug 31, 2022. It is now read-only.
rm spec issues re Object.create(null) & __proto__ #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
rm spec issues re Object.create(null) & proto
the previous code used the idiom of
Object.create(null)to use an object like a hash or cache, and leveraged the prototype chain as a type of cache miss failover. there is some js spec weirdness and changes around node 0.12 surrounding the existence of__proto__when usingObject.create(null).to eliminate this confusion i've added a function to replace the above so that the semantics are clear and consistent and we aren't using the non-standard
__proto__.also update npm dev deps to latest versions and added a missing jshintrc.