Olivier Deheurles

Once the API is stabilised we should add a wiki page to document the .NET API

review https://github.com/real-logic/simple-binary-encoding/issues/42

Review current generated code

1

Current generated code is very close to Java API, which is not very idiomatic for a C# developer. We need to go through the generated code and decide how the...

Groups API is not idiomatic .NET

1

I ported the java API which uses iterators to access groups. This makes the C# groups API very weird to use. We should review that but we should not introduce...

The schema contains optionally a description of the different properties, we should display that when available and also other information which can be useful during development (Optional/required, null_value, sinceVersion, Min/max...

Optional fields, exposed as C# properties should encapsulate null values (the value used to represent null, as defined here: https://github.com/WeAreAdaptive/simple-binary-encoding/blob/master/main/java/uk/co/real_logic/sbe/PrimitiveValue.java)

We may want to target portable class library and environments which won't be able to call unsafe code.

We want to define acceptance tests to validate the code generated is valid, from SBE spec perspective.

I'm not sure yet if we need that for everything, or per expression...