Repository navigation
Buffer.slice: Document behavior if end > slice.length #14714
Description
Activity
Care to submit a documentation PR?
- added a commit that references this issue
on Aug 9, 2017 - probably not going to have time :(On Wed, Aug 9, 2017 at 09:00 Colin Ihrig ***@***.***> wrote: Care to submit a documentation PR? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#14714 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOSI33bA21P3jLxjEBcKbC-5JvlsaCaks5sWdeOgaJpZM4OyQ7I> .--…-- Kevin Burke 925.271.7005 | kev.inburke.com
- added a commit that references this issue
on Aug 12, 2017 - Thank you!On Sat, Aug 12, 2017 at 14:17 Refael Ackermann ***@***.***> wrote: Closed #14714 <#14714> via 9cb3745 <9cb3745> . — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#14714 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOSIxFCX6U80aEua2oucTzM2UNQjsIJks5sXghwgaJpZM4OyQ7I> .--…-- Kevin Burke 925.271.7005 | kev.inburke.com
The documentation for Buffer.slice says this about end:
It does not describe what happens if end is greater than the length of the buffer. Does Node return a buffer of length (end - start) with zero values for the extra values? Does it return a shorter buffer? Does it throw a RangeError?