Miki
Miki
Review range checking template data as well. Please note that range check data are used by bitmask template data as well.
Another use case: ``` enum uint64 TestEnum { ONE, TWO, THREE }; struct Test { uint64 field1; uint32 field2 : field2 < field1; uint8 field3 : field3 < valueof(TestEnum.ONE); };...
All built-in zserio types (like uint8) which are mapped to C++ primitive types (like uint8_t) are initialized by calling of default constructor. Which actually means that such types are initialized...
Yes, this could be an option as well if we don't have time to implement something better as described in #203. We should probably change Java and Python generators in...
In the meantime, we can suggest as workaround to use always field constructor. This will ensure that all fields are initialized at once and any new additional field will cause...
We will try to make the first implementation applying the following **requirements**: 1. Schema authors should not be forced to decide at the beginning which type is relevant for forward/backward...
> Relates to #288 Thanks! :-)
Zserio language does not support SQLite indexes at all, so unfortunately this is not possible.
Yes, if there is a need to support SQLite indexes, we will probably implement it as you wrote. We just did not get any request to support SQLite indexes so...
Thanks for that, we will fix it in current milestone.