Yoshifumi Kawai
Yoshifumi Kawai
Thanks for the detailed report, this looks like a problem that needs to be fixed. I'll give it a try.
yes, I'll try it.
I am currently examining other issues as well, but I have not started working on this yet. If you send us a pull request, I will accept it.
Thank you! I've confirmed, it is bug of implementation, if exists array's covariance throws runtime exception. I'll fix it. For example, if you change to this will work fine. ```csharp...
ah, no, need to fix sorry.
Oh, Polyfill should be internal. I didn't check it carefully when I merged the PR. I'll fix it right now.
Hmm, but I don't want to provide my own ArrayBufferWriter... To be honest, I think the best thing to do is to remove the netstandard 2.0 support again.
UnityResolver with built-in Vector3 Formatter is not automatically registered in v3.0.54-alpha, so please include it in StaticCompositeResolver manually. This problem has been resolved in the latest v3 (not yet released).
Without everything being explicitly specified, unintended breaking changes are ultimately unavoidable. However, I believe it's more widely understood that serialization results can break due to name changes. This is because...
Since we can expect GUIDs to come in various formats, I agree with making the deserialization somewhat flexible. However, in the implementation, please be careful about unnecessary allocations. Also, it's...