Miki
Miki
Arguments of parameterized types for arrays are not checked at all during writing. Consider the following: ``` struct ArrayHolder(varsize size, uint8 extraLimit) { varuint array[size]; bit:3 extraValue : extraValue
Although floats comparison in zserio expressions are forbidden, there are still floats comparisons in generated code in equality operator and in parameter check. Such float comparison in generated code in...
Zserio runtime libraries can throw exceptions with generic message which described the problem. Such messages do not contain any detail information about problematic Zserio object which do not help users...
Currently, the generated Java Service interface for server forces users to use inheritance to implement protected methods: ``` public final class SimpleService { public static abstract class SimpleServiceService implements zserio.runtime.service.ServiceInterface...
ZserioError does not give any info on nested exceptions when thrown from ZserioIO. It just prints the message of the top exception. But especially in a remote invocation case this...
Currently, the 'Used By' section does not use full names with packages. There is only tooltip with package name. This can probably confuse users if there are multiple types with...
If the structure does not contain any packable field, Zserio compiler fires warning if such structure is used in packed array. However, if such packed array is used in template,...
Currently, the optional clause warning is not fired if ternary operator is used. This is because zserio is not able to check correctness of such expression. Example: ``` struct Data...
Consider the following documentation see tag where is an identifiers clash between type and field: ``` package test; subtype int32 Defined; struct Item { /** The following should be resolved...
Currently, the following steps are taken to resolve identifiers in expressions: 1. The identifier is looked up in local scope. 2. If not found, the identifier is looked up in...