Miki

It seems like this is a clang bug, clang-17 works without any problem. For time being, we will leave this exception in CI as it is.

Actually, the requirement that during writing the offsets should be initialized correctly and automatically together with no setters is very strict. Consider this: ``` struct Schema { uint32 myOffsetArray[]; uint8...

Actually, `varsize` is evil and it has been already disabled in Zserio. The problem was that you are not possible to calculate bit size of `varsize` in advance without knowing...

> **Dedicated Offset Types**: I support the idea of explicit types and don't see a problem with having different variants. @mikir, why do you think this could be too complicated?...

Because we have discussed 4 different ideas in this issue, I have created three new issues where we can continue discussions: #641 - Offset expressions should be disabled #642 -...

Don't forget to update documentation with some more detailed description of the offsets.

This is a little bit controversial because it really could break the backward compatibility for some user schemas. We will have to rethink it twice if we can afford to...

We will implement it only if this is absolutely necessary for [new C++17 generator](https://github.com/ndsev/zserio-cpp17). It has been moved to the backlog in the meantime.

We have enabled the following SonarCloud rules: - [Child class fields should not shadow parent class fields](https://sonarcloud.io/organizations/ndsev/rules?open=cpp%3AS2387&rule_key=cpp%3AS2387) - [Variables should not shadowed](https://sonarcloud.io/organizations/ndsev/rules?open=cpp%3AS1117&rule_key=cpp%3AS1117) Unfortunattely, SonarCloud have not caught anything. In spite...

We think that all reported issues where the identifer `allocator` is hiding an identifier...` are the false positives. All others issues (identifier `value`, `last` and `first`) will be fixed.