FUJI Goro
FUJI Goro
Ah, sorry! Misunderstood. There're some reasons that we cannot memorize them: * `instance.*Async()` are not async-await safe (or not thread-safe) * the instance has lots of configuration parameters so it's...
Sounds good. Will try it.
Not tested yet, because I have no project with web workers.
I think MessagePack is designed to handle fixed-sized data structures and it's not easy to handle your case. You can define your own protocol on the top of MessagePack, like...
@covert-encryption I'm not exactly sure about your use cases, but I'm willing to make some methods public (with some changes, if needed). Feel free to make pull-requests with tests that...
I'm not sure what you want exactly, but I'm afraid I have no plan to provide any code generation tools.
You can already use an Array as the data source of `encode()`, so once you "translate" your objects into arrays before passing them to `encode()`, the encoded objects will get...
Can you elaborate on your use case? In general, it's not a good idea to distinguish `null` and `undefined` in JavaScript, and supporting it with extension types could lead to...
Thank you for the contribution. We need to make sure it's safe when we use this PR in the async/await context.