Yoshifumi Kawai

Currently Utf8Json does not have like `ItemRequired = Required.Always` option. So can not do it.

@itn3000 is trying fast utf8 utf16 utilities. https://github.com/itn3000/unicode-convert-utilities @ufcpp is building custom UTF8 decoder. https://github.com/ufcpp/Utf8Utils `NStack` is golang like new encoding system. https://github.com/migueldeicaza/NStack `System.Text.Utf8String` is span based new primitive. https://github.com/dotnet/corefxlab/tree/master/src/System.Text.Utf8String/System/Text

Currently, this is by spec. It is necessary to think about whether to change.

Utf8Json supports .NET Standard 2.0. Currently UWP does not support .NET Standard 2.0. But VS preview may works, please try it and wait for fall creator update(?). https://blogs.msdn.microsoft.com/dotnet/2017/08/25/uwp-net-standard-2-0-preview/

VS 2017 version 15.4 supports .NET Standard 2.0 and UWP. https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes#15.4

Maybe requires code generation for AOT. https://github.com/neuecc/Utf8Json#pre-code-generationunityxamarin-supports

I think .NET Core 3 support is essential. Also, PR for some bugs will have to be merged. MessagePack-CSharp v2 work is nearing completion (this takes more than half a...

MessagePack-CSharp v2 is still rc(but few weeks, will complete). I've invesitgated new techniques, use IBufferWriter and ReadOnlySequence that exists after Utf8Json relased. MessagePack v2 takes care of memory usage and...

Oh, hmn, this is a bug of .NET Core 2.0 compiler...? https://github.com/dotnet/core/issues/902 If you can, build your mac from source-code?

UnityShims is for the .NET platform and should not be included in Unity.