Yoshifumi Kawai
Yoshifumi Kawai
I've finished API surface. ```csharp // IOverwriteMessagePackFormatter requires fallback standard formatter public interface IOverwriteMessagePackFormatter : IMessagePackFormatter { void DeserializeTo(ref T to, byte[] bytes, int offset, IFormatterResolver formatterResolver, out int readSize);...
Protocol Buffer's `Merge` is add for collection, not override. Which behavior is preferred? or implements both?(how to configure?)
concept of configuration per resolver. default is merge. ```csharp public class MessagePackConfiguration : IResolverConfiguration, IMessagePackFormatter { public static readonly MessagePackConfiguration Default = new MessagePackConfiguration(CollectionDeserializeToBehaviour.Merge); public CollectionDeserializeToBehaviour CollectionDeserializeToBehaviour { get; private...
Thanks, I'll implement both(and default is changed to overwrite).
v2 has biggest changes. Implements this feature require to finish v2 completely.
Merge/Overwrite API sometimes exists in serializers. For example, Unity has `static void FromJsonOverwrite (string json, object objectToOverwrite)` API. https://docs.unity3d.com/Manual/JSONSerialization.html My proposal API(`DeserializeTo`)'s use-case is based on it and I agree...
thanks, it seems good. approve to merge.
Environment: Windows 10 Pro x64 Intel Core i7-6700 3.40GHz 32GB RAM .NET 4.5 release build. `` Your code compare get-speed from context or static direct. I mentioned about serializer lookup...
Thank you, the answer is yes.
Here is csproj, launch VS2017 -> Reference NuGet -> Run. ```xml Exe netcoreapp1.0 ```