feat: encodeInto(obj, dest, [options]) #96
Draft
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.
@Gozala @alanshaw I was experimenting with this as an encode API - BYO
Uint8Array
. Unfortunately I can't really measure particularly amazing performance benefits from this, we're already attempting to do a bit of optimisation around allocation already; I think most of the bottlenecks are just in being tied toUint8Array
s and their perf limitations in the first place. But perhaps you have a use-case that would make this worthwhile?I'd have to spend a bit more timing cleaning this up and documenting but wanted to see if you had any input on the API and its utility before I bother.