Implementing Strict Array Bounds to Enhance User Safety and Prevent Out-of-Range Access #77
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.
JavaScript allows users to access values outside the range of an array, and as a consequence, some implementations of sorting and binary search algorithms that would fail in other languages work correctly in JavaScript, which in my opinion is incorrect.
I have created this PR to address this issue by adding a Proxy to throw an error when the user attempts to access a key that does not exist in the array.
Let's se a example:
This code seems correct, right?
And it passes the test
But there is an error on this code that can be caught using the strict array. On the inner loop, it access an index out of bound.