Ivan Shynkarenka
Ivan Shynkarenka
Will look into this issue! Thanks for reporting!
Fixed! Thanks for reporting! Can you please check the fix on your side?
I think it's possible to generate c# structs as partial if it not reduce the performance. Also I'm thinking about experimenting with new c# records instead of structs, because: 1)...
We're not competing with native language serializers, because we're cross platform, cross language and cross wire. The fastest serialize will be memcpy(sizeof(MyStruct)) in C++ :-)
It was easy to benchmark the same model as Colfer serialization does for testing the serialization performance. bench.fbe: ``` package bench version 1.0 struct Benchmark { int64 key; string host;...
Serialization benchmark results: ``` Phase: Serialize Average time: 31 ns/op Minimal time: 37 ns/op Maximal time: 39 ns/op Total time: 2.667 s Total operations: 86009850 Operations throughput: 32239885 ops/s ```...
Good point
FBE protocol spec allows to declare enums with duplicate values: ``` // Byte enum declaration enum EnumByte : byte { ENUM_VALUE_0; ENUM_VALUE_1 = 0; ENUM_VALUE_2; ENUM_VALUE_3 = 254; ENUM_VALUE_4; ENUM_VALUE_5...
Enum value string is rarely used outside struct's dumps in logs. So
My first priority is to create a port for IOS Swift only then I'll think over how to create a port for ANSI C