Make serialize() throw if same buffer and byteOffset are given
#29
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.
I cannot explain it better than I've done in the code and tests.
NOTES
We cannot do much magic here, and we should not make happy assumptions. For example, in Node.js when you create a Node native
Bufferinstance usingBuffer.allocUnsafe(), itsbuffermember (anArrayBufferinstance where the bytes really are) is a **very big allocatedArrayBufferinstance. If you later create another Node nativeBufferthen its.buffermember will be the same as in the previous one, however the byteOffset and so off are different: