Repository navigation
Remove buffer.get and buffer.set #4587
Description
Activity
Another advantage of removing these is that they'll stop shadowing the underlying
TypedArray.prototype.setfunction.- changed the title
[-]Deprecate `buffer.get` and `buffer.set`[/-][+]Remove `buffer.get` and `buffer.set`[/+]on Jan 8, 2016 Can be removed whenever. It never gets in the way of anything, so I keep forgetting about them. Wouldn't even say it's a major change. Not documented and have been fully deprecated going on 3 years (as @feross mentioned).
@trevnorris Okay, PR sent: #4594
- added a commit that references this issue
on Apr 2, 2016 - added a commit that references this issue
on Jun 3, 2016 - added a commit that references this issue
on Jul 27, 2026
These have been deprecated since Apr 27, 2013, and the plan was to remove them in "node v0.13", according to the comments.
buffer.get(index)is superseded bybuffer[index].buffer.set(index, value)is superseded bybuffer[index] = value.I haven't seen these used in real code, ever. They also have never been documented at any point in node's history, according to the git commit history for
doc/api/buffer.markdown.I think it is safe to finally remove these.
Thoughts?