| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Accessing prototype properties directly on a typed array will throw. So do an extra check in Buffer's own getters to verify it is being called on an instance. Fixes: nodejs#3297
|
LGTM |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
Isn't this a major change? Behaviour is not backward compatible, right? Earlier we used to throw and we don't now. |
Sorry, something went wrong.
|
@thefourtheye This was a bug from the change to using typed arrays. |
Sorry, something went wrong.
|
If you take notice of the change, we didn't remove an exception. It was throwing because of bad access to a typed array property. |
Sorry, something went wrong.
|
@trevnorris ... should this land in v4.x? ... nm... looking at it, there's no reason why not :-) |
Sorry, something went wrong.
Ah, fine then. Thanks for clarifying :-) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Accessing prototype properties directly on a typed array will throw. So
do an extra check in Buffer's own getters to verify it is being called
on an instance.
Fixes: #3297
R=@Fishrock123 ?
CI: https://ci.nodejs.org/job/node-test-pull-request/468/