Add a JSON.parse function which can receive re-usable objects from an object pool

[jdgriffith]

In certain high ingestion scenarios from a websocket, it might be advantageous to use an object pool of pre-initialized objects which can be used for JSON parsing where a new object does not need to be created. This could help in several ways as it could help tell the JSON parser the shape of the data and also no new memory needs to be allocated for the object. Once an object is finished being utilized by processing, it could be given back to the object pool. I'm not asking for Bun to create an API for an object pool (but I'm not opposed!) but I am asking for more logic on the JSON processing side - the ability to pass an object along with the JSON string.

JSON.parse(jsonString, objectToBePopulated)

or

JSON.parse(jsonString, objectPool)

I'm curious if my thought about this helping with performance would hold true in this scenario but it's an interesting thought. I wonder what others think of this proposal.

[jdgriffith]

I'm not sure how to communicate this to you - it's not about streams or the surrounding interfaces for transmitting or piping the data. Even your example above probably uses JSON.parse under the hood in new Response(v).json(), if that returns an object. I use streams all the time for large amounts of data and they are wonderful for that - super efficient and fast.

My post and performance concerns are only about JSON.parse and that's it. Plenty of other projects have explored the concept of super efficient JSON parsers, including using SIMD, and I'm not the first to explore more efficiency as it relates to JSON processing.